Bug 2118145

Summary: [abrt] Crash on memory corruption after flatpak app installation
Product: [Fedora] Fedora Reporter: Mateus Rodrigues Costa <mateusrodcosta>
Component: flatpakAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: amigadave, debarshir, gnome-sig, klember, mail, mcrha, rhughes, tomasz.szymanski
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3b42e4bf7997dbcdc8e981a02a6a69995dafe471
Whiteboard: abrt_hash:5bb25e0b22aee1a3469b78ffaec92762ecc2080d;VARIANT_ID=silverblue;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 15:30:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mateus Rodrigues Costa 2022-08-14 14:43:44 UTC
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

Comment 1 Mateus Rodrigues Costa 2022-08-14 14:43:48 UTC
Created attachment 1905455 [details]
File: backtrace

Comment 2 Mateus Rodrigues Costa 2022-08-14 14:43:49 UTC
Created attachment 1905456 [details]
File: core_backtrace

Comment 3 Mateus Rodrigues Costa 2022-08-14 14:43:50 UTC
Created attachment 1905457 [details]
File: cpuinfo

Comment 4 Mateus Rodrigues Costa 2022-08-14 14:43:51 UTC
Created attachment 1905458 [details]
File: dso_list

Comment 5 Mateus Rodrigues Costa 2022-08-14 14:43:52 UTC
Created attachment 1905459 [details]
File: environ

Comment 6 Mateus Rodrigues Costa 2022-08-14 14:43:53 UTC
Created attachment 1905460 [details]
File: limits

Comment 7 Mateus Rodrigues Costa 2022-08-14 14:43:54 UTC
Created attachment 1905461 [details]
File: maps

Comment 8 Mateus Rodrigues Costa 2022-08-14 14:43:55 UTC
Created attachment 1905462 [details]
File: mountinfo

Comment 9 Mateus Rodrigues Costa 2022-08-14 14:43:56 UTC
Created attachment 1905463 [details]
File: open_fds

Comment 10 Mateus Rodrigues Costa 2022-08-14 14:43:57 UTC
Created attachment 1905464 [details]
File: proc_pid_status

Comment 11 Mateus Rodrigues Costa 2022-08-14 14:43:58 UTC
Created attachment 1905465 [details]
File: var_log_messages

Comment 12 Milan Crha 2022-08-15 10:00:18 UTC
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?

Comment 13 Milan Crha 2022-08-16 13:02:35 UTC
I believe this is related to:
https://github.com/flatpak/flatpak/issues/3701

Comment 14 Mateus Rodrigues Costa 2022-08-16 20:33:36 UTC
(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.

Comment 15 Milan Crha 2022-08-18 05:52:15 UTC
*** Bug 2118402 has been marked as a duplicate of this bug. ***

Comment 16 Ben Cotton 2023-04-25 17:46:15 UTC
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.

Comment 17 Ludek Smid 2023-05-25 15:30:23 UTC
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.