GNOME Bugzilla – Bug 416966
crash in Epiphany Web Browser: Closing the last tab.
Last modified: 2007-03-11 11:19:36 UTC
Version: 2.17.92 What were you doing when the application crashed? Closing the last tab. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 System: Linux 2.6.20-1.2982.fc7 #1 SMP Fri Mar 9 17:39:27 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 240787456 vsize: 240787456 resident: 110628864 share: 26501120 rss: 110628864 rss_rlim: 4294967295 CPU usage: start_time: 1173562039 rtime: 40292 utime: 37182 stime: 3110 cutime:24 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100 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) [Thread debugging using libthread_db enabled] [New Thread -1208297760 (LWP 20427)] [New Thread -1275573360 (LWP 27247)] (no debugging symbols found) 0x00184402 in __kernel_vsyscall ()
+ Trace 117595
Thread 1 (Thread -1208297760 (LWP 20427))
----------- .xsession-errors (6 sec old) --------------------- ** (epiphany:20427): WARNING **: No listener with the specified listener id 25 ** (epiphany:20427): WARNING **: No listener with the specified listener id 26 ** (epiphany:20427): WARNING **: No listener with the specified listener id 27 ** (epiphany:20427): WARNING **: No listener with the specified listener id 28 (epiphany:20427): GLib-CRITICAL **: g_hash_table_foreach_remove: assertion `hash_table != NULL' failed (epiphany:20427): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 351972 ***