FS#46722 - [pidgin] Crashing, possibly during blist sound notification.

Attached to Project: Arch Linux
Opened by Jonathan Ryan (jryan) - Wednesday, 14 October 2015, 20:35 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 17 December 2015, 03:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Pidgin crashed. I've opened a bug here instead of on Pidgin's bug tracker because it seems to be gstreamer related, and I've noticed to gstreamer things going on in recent package history?

If you don't think this is caused by us, then let me know so I can move it over to pidgin's bug tracker instead.

Additional info:

- pidgin-2.10.11-6
- bt.log (attached) is a gdb backtrace is with pidgin debug symbols from abs at version pidgin-2.10.11-5


Steps to reproduce:

Open pidgin, and run it for a while. Seems to randomly crash. Looking at the backtrace, it seems related to gstreamer notification?

If I need more debug symbols or did this wrong just let me know. This is first time I've reported a bug. Thanks.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 17 December 2015, 03:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  pidgin 2.10.11-6
Comment by Jonathan Ryan (jryan) - Wednesday, 14 October 2015, 20:50 GMT
I re-compiled gstreamer with debug symbols as well. Attached is an update backtrace.

pkg: gstreamer-1.6.0-1
Comment by Jonathan Ryan (jryan) - Wednesday, 21 October 2015, 15:15 GMT
Crash just happened again. Attached another backtrace. pidign, and libpurple, 2.10.11-5 with debug symbols.



   crash.log (5.5 KiB)
Comment by Jonathan Ryan (jryan) - Wednesday, 21 October 2015, 15:17 GMT
Should I file upstream instead? Is there anything I can do more to help? Thanks.
Comment by Evangelos Foutras (foutrelis) - Thursday, 22 October 2015, 04:31 GMT
(I deleted your first two backtraces because they contained the email of one of your contacts.)

Indeed, we recently started packaging the tip of the release-2.x.y branch which supports GStreamer 1.0.

Fedora and Ubuntu appear to be affected as well, but I couldn't find an upstream ticket in Pidgin's tracker. (Feel free to file one!)

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1206363
[2] https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1479715
Comment by dx (dx) - Thursday, 17 December 2015, 00:27 GMT
Upstream bug (fixed): https://developer.pidgin.im/ticket/16752

Judging by the hg revision in the 2.10.11-6 package, this is already fixed. I also can't reproduce it with this revision.

Test case:

1. Set the file descriptor limit low enough to be able to login, plus a few extra. "ulimit -Sn 20" works for me
2. Start pidgin
3. Send 10 messages or so, enough to hit that limit
4. Acquire crash

Loading...