Bug 2144929

Summary: [abrt] pidgin: g_malloc0(): pidgin killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: pidginAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 37CC: igor.raits, jskarvad, mcatanza, paul, rdieter, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b7912fbb29d987133c2106d0a9c0e0cc27689ded
Whiteboard: abrt_hash:c0828960225be129fd3bb6b7ab31e64528fdda68;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-19 17:52:57 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

Description Brian J. Murrell 2022-11-22 19:21:38 UTC
Description of problem:
Closing a conversation tab

Version-Release number of selected component:
pidgin-2.14.10-2.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-pidgin-733541.scope
cmdline:        pidgin -d
crash_function: g_malloc0
executable:     /usr/bin/pidgin
journald_cursor: s=783093dbf59a4c3e8293268cee3b547c;i=ad0486;b=bd5bccca569d409ea70859556dad085e;m=3384b3843;t=5ee12cc714df6;x=34e71605be30daf3
kernel:         6.0.9-300.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 1 Brian J. Murrell 2022-11-22 19:21:42 UTC
Created attachment 1926455 [details]
File: backtrace

Comment 2 Brian J. Murrell 2022-11-22 19:21:43 UTC
Created attachment 1926456 [details]
File: core_backtrace

Comment 3 Brian J. Murrell 2022-11-22 19:21:44 UTC
Created attachment 1926457 [details]
File: cpuinfo

Comment 4 Brian J. Murrell 2022-11-22 19:21:45 UTC
Created attachment 1926458 [details]
File: dso_list

Comment 5 Brian J. Murrell 2022-11-22 19:21:46 UTC
Created attachment 1926459 [details]
File: environ

Comment 6 Brian J. Murrell 2022-11-22 19:21:47 UTC
Created attachment 1926460 [details]
File: limits

Comment 7 Brian J. Murrell 2022-11-22 19:21:48 UTC
Created attachment 1926461 [details]
File: maps

Comment 8 Brian J. Murrell 2022-11-22 19:21:49 UTC
Created attachment 1926462 [details]
File: mountinfo

Comment 9 Brian J. Murrell 2022-11-22 19:21:51 UTC
Created attachment 1926463 [details]
File: open_fds

Comment 10 Brian J. Murrell 2022-11-22 19:21:52 UTC
Created attachment 1926464 [details]
File: proc_pid_status

Comment 11 Brian J. Murrell 2022-11-26 20:36:23 UTC
Similar problem has been detected:

Clicked on a conversation tab.  Boom.  Crash.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-pidgin-1100472.scope
cmdline:        pidgin -d
crash_function: g_malloc0
executable:     /usr/bin/pidgin
journald_cursor: s=783093dbf59a4c3e8293268cee3b547c;i=b0199e;b=bd5bccca569d409ea70859556dad085e;m=2d778388ac;t=5ee3d0ba99e5f;x=bff13a706e904823
kernel:         6.0.9-300.fc37.x86_64
package:        pidgin-2.14.10-2.fc37
reason:         pidgin killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 12 Brian J. Murrell 2022-12-19 16:00:37 UTC
Can any progress on this be made?  It's quite hideous to try to keep up with conversations when one has to have (literally) dozens of idle conversation tabs open because trying to close one crashes pidgin due to it trying to malloc some insanely huge amount of memory.

Is this even likely a problem in pidgin?  Pidgin only moved 2 bug-fix releases since it didn't have this problem in F36:

    Upgrade       pidgin-2.14.10-2.fc37.x86_64
    Upgraded      pidgin-2.14.8-5.fc36.x86_64

Or is this more likely a problem in libgtk (or some other supporting library?)

FWIW, I rebuilt 2.14.8-4 on F37 and it's having the same problems so this does not seem like a pidgin problem but perhaps it's gtk.  I'm going to change the Component based on that assumption.

Comment 13 Brian J. Murrell 2022-12-19 16:01:11 UTC
Er, I meant glib, not gtk.

Comment 14 Brian J. Murrell 2022-12-19 16:10:18 UTC
Hrm.  On second thought, perhaps it is actually gtk?  I will leave it with glib for the time being and let one of the maintainers there decide if this was gtk.

Comment 15 Stu Tomlinson 2022-12-19 17:15:49 UTC
It might have been pidgin all along - does https://bodhi.fedoraproject.org/updates/FEDORA-2022-da20dfbcfb fix it?

Comment 16 Brian J. Murrell 2022-12-19 17:30:18 UTC
Indeed.  https://bodhi.fedoraproject.org/updates/FEDORA-2022-da20dfbcfb does fix it.

Thanks much!

Comment 17 Michael Catanzaro 2022-12-19 17:38:47 UTC
It's a little weird that GLib is trying to allocate 10 TB of memory when *destroying* the hash table, though. Pidgin didn't *directly* cause that. I figure pidgin must have done something very messed up to wind up in that situation in the first place, but I wonder if GHashTable does something wrong when the size of the hash table is sufficiently large....

Comment 18 Brian J. Murrell 2022-12-19 17:46:58 UTC
Duplicate of bug #2112810.  Also reported upstream at https://issues.imfreedom.org/issue/PIDGIN-17702 but BZ doesn't seem to know about https://issues.imfreedom.org as it complains when trying to add to this ticket's Links.

Comment 19 Michael Catanzaro 2022-12-19 17:52:57 UTC

*** This bug has been marked as a duplicate of bug 2112810 ***

Comment 20 Michael Catanzaro 2022-12-19 17:53:38 UTC
OK, I see it's just bad memory. Cool.