Crash or hang when closing conversation windows
Tomasz Wasilczyk
tomkiewi at gmail.com
Sat Jan 26 08:32:45 EST 2013
Are you sure, that your Pidgin is built with this patch applied? I'm
pretty sure, that pointed revision *fixes* the problem (I had exactly
the same backtrace before writing it).
And here is the patch, which broken this for me:
http://hg.pidgin.im/pidgin/main/rev/f7b7a6c58ad3 (both are in
release-2.x.y, but not in 2.10.6).
BR,
Tomek
2013/1/26 Andrew Victor <avictor.za at gmail.com>:
> hi,
>
> I've started noticing (last +-2 months) Pidgin occasionally crashing
> or hanging when closing conversation windows.
> This is running the release-2.x.y branch (on Ubuntu 12.04)
>
> I cannot seem to reproduce the issue, so I've started running Pidgin under GDB.
>
> Here is a backtrace of the crash:
>
> Program received signal SIGSEGV, Segmentation fault.
> purple_conversation_get_account (conv=0xf) at conversation.c:693
> 693 return conv->account;
> (gdb) bt
> #0 purple_conversation_get_account (conv=0xf) at conversation.c:693
> #1 0x0809e341 in close_conv_cb (button=0x0, gtkconv=0x8955688) at gtkconv.c:234
> #2 0x0809e432 in pidgin_conv_window_destroy (win=0x89a5908) at gtkconv.c:9385
> #3 0x0809e800 in close_win_cb (w=0x8c4ea28, e=0x8955728, d=0x89a5908)
> at gtkconv.c:8367
> #4 0xb79df8a2 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #5 0xb765f484 in g_closure_invoke () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #6 0xb76710d9 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #7 0xb7678ff5 in g_signal_emit_valist () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #8 0xb7679453 in g_signal_emit () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #9 0xb7b19413 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #10 0xb79de0d4 in gtk_main_do_event () from
> /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #11 0xb784f758 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
> #12 0xb759fd86 in g_main_context_dispatch () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
> #13 0xb75a0125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #14 0xb75a056b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #15 0xb79dcb8f in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #16 0x0806d9f7 in main (argc=1, argv=0xbffff274) at gtkmain.c:934
>
>
> And here's a backtrace when it hangs:
>
> Program received signal SIGTSTP, Stopped (user).
> 0x08067b30 in purple_conversation_get_type at plt ()
> (gdb) bt
> #0 0x08067b30 in purple_conversation_get_type at plt ()
> #1 0x0809e355 in close_conv_cb (button=0x0, gtkconv=0x8482780) at gtkconv.c:237
> #2 0x0809e432 in pidgin_conv_window_destroy (win=0x8af6888) at gtkconv.c:9385
> #3 0x0809e800 in close_win_cb (w=0x890d5c0, e=0x8954238, d=0x8af6888)
> at gtkconv.c:8367
> #4 0xb79df8a2 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #5 0xb765f484 in g_closure_invoke () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #6 0xb76710d9 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #7 0xb7678ff5 in g_signal_emit_valist () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #8 0xb7679453 in g_signal_emit () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #9 0xb7b19413 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #10 0xb79de0d4 in gtk_main_do_event () from
> /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #11 0xb784f758 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
> #12 0xb759fd86 in g_main_context_dispatch () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
> #13 0xb75a0125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #14 0xb75a056b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
> #15 0xb79dcb8f in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #16 0x0806d9f7 in main (argc=1, argv=0xbffff284) at gtkmain.c:934
>
>
> I looked through the change-log, and noticed this possible change:
> < http://hg.pidgin.im/pidgin/main/rev/ab10a481e30f >
>
>
> Regards,
> Andrew Victor
More information about the Devel
mailing list