I have dbus-0.61. When starting multiple epiphany instances I've got the following crash. The similar problem is reported in other apps: https://lists.ubuntu.com/archives/ubuntu-mono/2006-April/000605.html Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208744272 (LWP 2492)] 0xb7f66402 in __kernel_vsyscall () #0 0xb7f66402 in __kernel_vsyscall () #1 0x00a22a13 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0x00164086 in gnome_init_with_popt_table () from /usr/lib/libgnomeui-2.so.0 #3 <signal handler called> #4 0xb7f66402 in __kernel_vsyscall () #5 0x00612159 in raise () from /lib/libc.so.6 #6 0x006136e3 in abort () from /lib/libc.so.6 #7 0x07c26275 in dbus_malloc () from /lib/libdbus-1.so.2 #8 0x07c100c7 in dbus_watch_set_data () from /lib/libdbus-1.so.2 #9 0x07be178b in dbus_connection_free_preallocated_send () from /lib/libdbus-1.so.2 #10 0x00c92160 in dbus_g_connection_unref () from /usr/lib/libdbus-glib-1.so.2 #11 0x08081f05 in _ephy_dbus_startup () #12 0x08081f7e in _ephy_dbus_startup () #13 0x00bca2fc in g_object_unref () from /lib/libgobject-2.0.so.0 #14 0x080813f4 in _ephy_dbus_release () #15 0x080810f2 in main () Thread 1 (Thread -1208744272 (LWP 2492)): #0 0xb7f66402 in __kernel_vsyscall () No symbol table info available. #1 0x00a22a13 in __waitpid_nocancel () from /lib/libpthread.so.0 No symbol table info available. #2 0x00164086 in gnome_init_with_popt_table () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #3 <signal handler called> No symbol table info available. #4 0xb7f66402 in __kernel_vsyscall () No symbol table info available. #5 0x00612159 in raise () from /lib/libc.so.6 No symbol table info available. #6 0x006136e3 in abort () from /lib/libc.so.6 No symbol table info available. #7 0x07c26275 in dbus_malloc () from /lib/libdbus-1.so.2 No symbol table info available. #8 0x07c100c7 in dbus_watch_set_data () from /lib/libdbus-1.so.2 No symbol table info available. #9 0x07be178b in dbus_connection_free_preallocated_send () from /lib/libdbus-1.so.2 No symbol table info available. #10 0x00c92160 in dbus_g_connection_unref () from /usr/lib/libdbus-glib-1.so.2 No symbol table info available. #11 0x08081f05 in _ephy_dbus_startup () No symbol table info available. #12 0x08081f7e in _ephy_dbus_startup () No symbol table info available. #13 0x00bca2fc in g_object_unref () from /lib/libgobject-2.0.so.0 No symbol table info available. #14 0x080813f4 in _ephy_dbus_release () No symbol table info available. #15 0x080810f2 in main () No symbol table info available.
Is it possible to try the version of dbus in CVS? There was a double free fix and threading fixes. Also make sure epiphany turns on threading early with dbus_g_threads_init
I don't need to call the dbus thread init function if I don't use dbus before gnome_vfs_init(), right? The first thing in epiphany's main is gnome_program_init which calls gnome_vfs_init which calls dbus_g_thread_init, and only afterward I use dbus.
So I am running D-Bus 0.91 and I am not seeing this crash. I bet this is fixed in CVS.
Looking at the bt again it looks like this has been fixed in the latest releases. It looks like an unref of a shared connection. We now hold a ref to the connection internally so crashes like this don't happen.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.