pidgin crashed with signal 5 in g_logv()

[BenChina]

Binary package hint: pidgin

pidgin crashed 5 times in 10 minutes

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Jul 1 21:26:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: cdrom
Package: pidgin 1:2.0.2-0ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/benjamin
ProcEnviron:
 LANGUAGE=zh_CN.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: pidgin
StacktraceTop:
 g_logv () from /usr/lib/libglib-2.0.so.0
 g_log () from /usr/lib/libglib-2.0.so.0
 g_malloc () from /usr/lib/libglib-2.0.so.0
 g_memdup () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/purple-2/libqq.so
Title: pidgin crashed with signal 5 in g_logv()
Uname: Linux benjamin-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_logv (log_domain=<value optimized out>, log_level=G_LOG_LEVEL_ERROR, format=0xb775c12c "%s: failed to allocate %lu bytes",
IA__g_log (log_domain=0xb7755146 "GLib", log_level=G_LOG_LEVEL_ERROR, format=0xb775c12c "%s: failed to allocate %lu bytes")
IA__g_malloc (n_bytes=4294967291) at /build/buildd/glib2.0-2.13.5/glib/gmem.c:135
IA__g_memdup (mem=0xbf8cf78a, byte_size=4294967291) at /build/buildd/glib2.0-2.13.5/glib/gstrfuncs.c:108
_qq_process_recv_normal_im_text (data=0xbf8cf6f0 "(Of�02\n", cursor=0xbf8cf7d0, len=<value optimized out>, common=0xbf8cf630,

[Sebastien Bacher (seb128)]

Thank you for your bug

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Have you been able to reproduce this with an up to date Ubuntu system ?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

[zertyz (zertyz)]

I'd like to reopen this bug since it still happens and I have more information to provide. Please see my post. Thanks

[zertyz (zertyz)]

Using Pidgin 2.4.3 on an updated system it quits suddenly from time to time. Investigating by running "pidgin -d" I found that it attempts to allocate a huge amount of memory which is, of course, denied and then it quits. Investigating a little further I found the pattern: whenever pidgin tried to open a new httpcon for an specific contact of mine -- maybe because the contact attempted to talk to me or to retrieve my picture or changed the nick... i'm not sure. To add: I'm using the MSN protocol.

In short: this bug is hard to track because it depends on contact behaviour but it turns out to make pidgin useless since I cannot establish a serious conversation with no one.

I see two problems:

  1) The main bug, of course: pidgin should not try to allocate, for any reason, that huge amount of memory (about 100 gigabytes or so)
  2) The behavior when pidgin cannot allocate memory shouldn't be to simply quit. I'd suggest that only the operation that demanded that memory gets aborted, not the whole application. That way hopefully pidgin could stay running and, possibly, without even the user noticing that something went wrong.

and... if you allow me:

  3) If one would attempt to make pidgin rock solid i'd suggest that it never discards a message: if the application quits (or gets killed) before the user can read the message, when started over again the unseen messages should be shown.

[zertyz (zertyz)]

...

It just happened again:

here is the last log lines that use to happen just before pidgin quits:

(18:04:15) msn: C: SB 025: MSG 20 D 143
(18:04:15) msn: C: NS 000: PNG
(18:04:15) msn: S: SB 025: ACK 20
(18:04:15) msn: S: NS 000: QNG 49
(18:04:17) msn: C: SB 024: MSG 11 D 795
(18:04:17) msn: S: SB 024: ACK 11
(18:04:17) msn: S: SB 024: MSG <email address hidden> (B)Felipe%20Magalhães%20-%20AtivaTrade 143
(18:04:17) msn: S: SB 024: MSG <email address hidden> (B)Felipe%20Magalhães%20-%20AtivaTrade 484
(18:04:17) GLib: /tmp/buildd/glib2.0-2.16.6/glib/gmem.c:136: failed to allocate 1493237761 bytes

[Chris Coulson (chrisccoulson)]

zertyz - if you are experiencing a crash, then please have Apport submit a new crash report so it can be processed properly by the retracer. You haven't posted anything here to suggest that you are experiencing the same bug.

To do this, you might need to enable Apport in /etc/default/apport and then restart. Once you have done this, please repeat the steps necessary to recreate the crash.

If you don't see a crash notification and you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm going to close this bug again as the process detailed above will open a new report for you, and there was no response from the original reporter of this bug.

Thanks