Hide Forgot
Version-Release number of selected component: dnf-4.2.5-2.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/bin/python3 /bin/dnf upgrade crash_function: mem_error executable: /usr/bin/python3.7 journald_cursor: s=74bc29a2da0e425b9a2de84f0b36a37a;i=541c;b=2ac8d39cb9344d5ab7937c83d358623f;m=5f43d9bbfe;t=58e96115903c6;x=88c883713d7fa6fc kernel: 5.1.18-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: 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] File: _var_log_dnf.log
Created attachment 1593727 [details] File: backtrace
Created attachment 1593728 [details] File: cgroup
Created attachment 1593729 [details] File: core_backtrace
Created attachment 1593730 [details] File: cpuinfo
Created attachment 1593731 [details] File: dnf-makecache.log
Created attachment 1593732 [details] File: dso_list
Created attachment 1593733 [details] File: environ
Created attachment 1593734 [details] File: limits
Created attachment 1593735 [details] File: maps
Created attachment 1593736 [details] File: mountinfo
Created attachment 1593737 [details] File: open_fds
Created attachment 1593738 [details] File: proc_pid_status
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.