pidgin crashed when sending offline msn message

Bug #319576 reported by BlueT - Matthew Lien - 練喆明
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

matthew@Priapus:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
matthew@Priapus:~$ LANG="C" apt-cache policy pidgin
pidgin:
  Installed: 1:2.5.2-0ubuntu1
  Candidate: 1:2.5.2-0ubuntu1
  Version table:
 *** 1:2.5.2-0ubuntu1 0
        500 http://ftp.twaren.net intrepid/main Packages
        100 /var/lib/dpkg/status

I got offline msg when I login to msn,
I replied some msg as usual, the first few lines could send, but when I typed in the last mag and hit [Enter], pidgin crashed.

Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :
Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :
Revision history for this message
BlueT - Matthew Lien - 練喆明 (bluet) wrote :
Revision history for this message
Pekka Vuorela (pvuorela-iki) wrote :

This might be the same bug I'm experiencing. Common case for me is contact going offline in a conversation, after which I try to send a message, resulting in Pidgin crashing.

Just ran it on gdb:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb70e7700 (LWP 22960)]
0xb61f2052 in ?? () from /usr/lib/purple-2/libmsn.so
(gdb) bt
#0 0xb61f2052 in ?? () from /usr/lib/purple-2/libmsn.so
#1 0xb7841e26 in g_timeout_dispatch (source=0xa981318, callback=0, user_data=0xa966fa8)
    at /build/buildd/glib2.0-2.18.2/glib/gmain.c:3589
#2 0xb78416f8 in IA__g_main_context_dispatch (context=0xa053968) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2144
#3 0xb7844da3 in g_main_context_iterate (context=0xa053968, block=1, dispatch=1, self=0xa02c3e8)
    at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2778
#4 0xb78452c2 in IA__g_main_loop_run (loop=0xa4a0318) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2986
#5 0xb7b503a9 in IA__gtk_main () at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c:1200
#6 0x080caaaf in main ()

Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

pidgin goes into a loop consuming all RAM and CPU. Presumably the segfault is related to a malloc failure.

Revision history for this message
Monkey (monkey-libre) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

This bug was so serious that I am no longer a pidgin or msn user. The impact on the overall stability of my system was simply too high.

See http://www.jwz.org/doc/cadt.html for a description of why this bug will expire.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

Changed in pidgin (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.