Version-Release number of selected component:
cmdline: /usr/bin/python3 /bin/dnf upgrade
runlevel: N 5
Thread no. 1 (10 frames)
#2 mem_error at ../glib/gslice.c:1476
#3 slab_allocator_free_chunk at ../glib/gslice.c:1353
#4 magazine_cache_trim at ../glib/gslice.c:678
#5 magazine_cache_push_magazine at ../glib/gslice.c:709
#6 thread_memory_magazine2_unload at ../glib/gslice.c:1117
#7 g_slice_free1 at ../glib/gslice.c:1117
#8 g_type_free_instance at ../gobject/gtype.c:1943
#9 package_dealloc at /usr/src/debug/libdnf-0.31.0-3.fc30.x86_64/python/hawkey/package-py.cpp:84
#10 subtype_dealloc at /usr/src/debug/python3-3.7.3-3.fc30.x86_64/Objects/typeobject.c:1256
#11 list_dealloc at /usr/src/debug/python3-3.7.3-3.fc30.x86_64/Objects/listobject.c:324
Created attachment 1593726 [details]
Created attachment 1593727 [details]
Created attachment 1593728 [details]
Created attachment 1593729 [details]
Created attachment 1593730 [details]
Created attachment 1593731 [details]
Created attachment 1593732 [details]
Created attachment 1593733 [details]
Created attachment 1593734 [details]
Created attachment 1593735 [details]
Created attachment 1593736 [details]
Created attachment 1593737 [details]
Created attachment 1593738 [details]
Thank you very much for your report. Please could you still reproduce the issue or it appears only once?
I don't know how it happened, and I have only seen it once.
I am sorry but this quite difficult to investigate such an issue without a reproducer.
Please could you provide an output from command "valgrind dnf upgrade -y" (It performs upgrade, but also it monitors usage of resources. It takes really very long time to finish)? Probably there could be a hint.
I told you it has only happened once. I can't reproduce it.
Thank you very much for your report. It looks like that the issue was with a usage of memory. The issue also appeared only once. It is possible that the issue was not related to dnf, or that the issue was already fixed. Unfortunately without a reproducer we cannot do much.