pidgin crashed with SIGSEGV in malloc()

[Hari]

Binary package hint: pidgin

I left it running for some time.

Note that pidgin fails to run normally -- I had to use MALLOC_CHECK_=0 to get it to run.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Jan 9 22:23:44 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.2.2-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcCwd: /home/harinath
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/harinath/bin:/home/harinath/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 LANGUAGE=en_IN:en
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 ?? () from /usr/lib/libpng12.so.0
 png_create_read_struct_2 ()
Title: pidgin crashed with SIGSEGV in malloc()
Uname: Linux hariville.hurrynot.org 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse-rt sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate () from /lib/libc.so.6
_int_malloc () from /lib/libc.so.6
malloc () from /lib/libc.so.6
png_create_struct_2 (type=<value optimized out>, malloc_fn=0x1abbc80,
png_create_read_struct_2 (user_png_ver=0x2aaaaafae42e "1.2.15beta5",

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Max Randor (max-randor)]

I am getting this bug when running pidgin on Intrepid Ibex.
This bug occurs before pidgin has finished loading - it never displays a window or an icon in the notification area. This bug has occured for me since my upgrade from hardy to intrepid.
I tried to use apport to submit a bug - but I think it was stopped by some sort of firewall so the bug report it would have sent is attached.

[Max Randor (max-randor)]

A work around that works for me is to disable use the same proxy for all protocols in gnome proxy settings.
see: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/271698

[Khorne (szczygiel-piotr)]

Everything seems to be ok with newest pidgin on jaunty alpha

[Bas232 (bas-heppen)]

I allready found the solution, simply turn all sounds off and it doesn't
crash anymore.

Op zaterdag 07-02-2009 om 21:17 uur [tijdzone +0000], schreef Khorne:
> Everything seems to be ok with newest pidgin on jaunty alpha
>

[Khorne (szczygiel-piotr)]

It crashed once again with newest updates on Jaunty alpha during application close - auto raport was generated

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

Could you try on jaunty now?

[shendra3 (shendra3)]

On Wed, 2009-04-29 at 21:11 +0000, Sebastien Bacher wrote:
> Could you try on jaunty now?
>

i've already use jaunty, and everything work well.

tnx

[Andreas Moog (ampelbein)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.