Version-Release number of selected component: gnome-software-42.4-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-2581.scope cmdline: /usr/bin/gnome-software --gapplication-service crash_function: ptr_array_free executable: /usr/bin/gnome-software journald_cursor: s=3e920f15c66b4d42b068eb649a486e32;i=59292;b=f030c81163b045fc8b9c7e6e73c88117;m=97b790e2;t=5e6344f89a409;x=22b87a67aafd0b00 kernel: 5.18.16-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1905455 [details] File: backtrace
Created attachment 1905456 [details] File: core_backtrace
Created attachment 1905457 [details] File: cpuinfo
Created attachment 1905458 [details] File: dso_list
Created attachment 1905459 [details] File: environ
Created attachment 1905460 [details] File: limits
Created attachment 1905461 [details] File: maps
Created attachment 1905462 [details] File: mountinfo
Created attachment 1905463 [details] File: open_fds
Created attachment 1905464 [details] File: proc_pid_status
Created attachment 1905465 [details] File: var_log_messages
Thanks for a bug report. I see the reason for the crash is: malloc_consolidate(): unaligned fastbin chunk detected which means there happened some sort of memory corruption (usually caused by the code, like when writing to an already freed memory or such things). These are usually quite hard to reproduce and even this one had been detected while the flatpak plugin had been refreshing its data, it doesn't mean it's the place where the memory corruption happened. By any chance, do you have steps to reproduce this crash, please?
I believe this is related to: https://github.com/flatpak/flatpak/issues/3701
(In reply to Milan Crha from comment #12) > Thanks for a bug report. I see the reason for the crash is: > > malloc_consolidate(): unaligned fastbin chunk detected > > which means there happened some sort of memory corruption (usually caused by > the code, like when writing to an already freed memory or such things). > These are usually quite hard to reproduce and even this one had been > detected while the flatpak plugin had been refreshing its data, it doesn't > mean it's the place where the memory corruption happened. > > By any chance, do you have steps to reproduce this crash, please? I believe I ran `flatpak update` while Gnome Software was checking for updates.
*** Bug 2118402 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.