Segfault on File Exit

[GoogleCodeExporter]

Platform: Ubuntu 10.04 Lucid and 9.10 Karmic
Software version: chmsee-1.2.0-rc1.tar.gz

Choosing File > Exit causes a segfault.

gdb backtrace in Ubuntu 10.04 Lucid:

build$ gdb chmsee
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/bin/chmsee...(no debugging symbols 
found)...done.
(gdb) r
Starting program: /usr/local/bin/chmsee 
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e19b70 (LWP 16072)]
[New Thread 0xb7618b70 (LWP 16073)]
[New Thread 0xb6e17b70 (LWP 16074)]
[New Thread 0xb6616b70 (LWP 16075)]

(chmsee:16069): GLib-GObject-CRITICAL **: g_type_instance_get_private: 
assertion `instance != NULL && instance->g_class != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
0x0806193a in cs_chmfile_get_bookfolder ()
(gdb) bt
#0  0x0806193a in cs_chmfile_get_bookfolder ()
#1  0x08054875 in chmsee_quit ()
#2  0x00945dcc in g_cclosure_marshal_VOID__VOID () from 
/usr/lib/libgobject-2.0.so.0
#3  0x00938252 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#4  0x0094c99d in ?? () from /usr/lib/libgobject-2.0.so.0
#5  0x0094ddb4 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6  0x0094e256 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#7  0x002bcda5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8  0x002beead in gtk_action_activate () from /usr/lib/libgtk-x11-2.0.so.0
#9  0x00945dcc in g_cclosure_marshal_VOID__VOID () from 
/usr/lib/libgobject-2.0.so.0
#10 0x009368b9 in ?? () from /usr/lib/libgobject-2.0.so.0
#11 0x00938252 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#12 0x0094c23a in ?? () from /usr/lib/libgobject-2.0.so.0
#13 0x0094ddb4 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#14 0x0094e256 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#15 0x004c6315 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0
#16 0x003a48e0 in gtk_menu_shell_activate_item () from 
/usr/lib/libgtk-x11-2.0.so.0
#17 0x003a624f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x0039bba4 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x00395364 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#20 0x009368b9 in ?? () from /usr/lib/libgobject-2.0.so.0
#21 0x00938252 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#22 0x0094c5e6 in ?? () from /usr/lib/libgobject-2.0.so.0
#23 0x0094dc33 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#24 0x0094e256 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#25 0x004c2566 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#26 0x0038d99d in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x0038ed47 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x0068339a in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#29 0x009bb5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x009bf2d8 in ?? () from /lib/libglib-2.0.so.0
#31 0x009bf817 in g_main_loop_run () from /lib/libglib-2.0.so.0
#32 0x0038f309 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#33 0x080525a4 in main ()
(gdb) q

An identical backtrace happens when running the second time and choosing File > 
Exit.

In Ubuntu 9.10 Karmic, an identical backtrace is produced, except with 
different addresses. And running a second time in Karmic produces the same 
backtrace again.

I saw xulrunner mentioned in another issue, so just in case it's of any 
relevance:
In Lucid I have installed:
 * xulrunner-1.9.2 version 1.9.2.3+nobinonly-0ubuntu2
 * xulrunner-1.9.2-dev version 1.9.2.3+nobinonly-0ubuntu2

In Karmic I have installed xulrunner-1.9.1, xulrunner-1.9.1-dev, and 
xulrunner-1.9.1-gnome-support.

Original issue reported on code.google.com by strobert@gmail.com on 10 Jun 2010 at 10:31

[GoogleCodeExporter]

Thank you reporting this. Bugfix has been committed to github.

Original comment by jungl...@gmail.com on 12 Jun 2010 at 5:04

• Changed state: FixCommited

[GoogleCodeExporter]

I can confirm that this is fixed in 4a3b7fe80cb625c5467635e82b1f0de576424a17 
(2010-06-11). Thanks!

Original comment by strobert@gmail.com on 14 Jun 2010 at 10:34

[GoogleCodeExporter]

Fixed in chmsee-1.2.0-rc2

Original comment by jungl...@gmail.com on 28 Jun 2010 at 8:24

• Changed state: Fixed