GNOME Bugzilla – Bug 597896
crash in Epiphany Web Browser: Running epiphany -- it c...
Last modified: 2009-10-09 11:39:10 UTC
Version: 2.26.3 What were you doing when the application crashed? Running epiphany -- it crashes all the time now. Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Darklooks Icon Theme: Neu GTK+ Modules: gnomebreakpad Memory status: size: 186707968 vsize: 186707968 resident: 48107520 share: 24014848 rss: 48107520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255086553 rtime: 1748 utime: 1658 stime: 90 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-gecko' [Thread debugging using libthread_db enabled] [New Thread 0xaf6e9b90 (LWP 15930)] [New Thread 0xb203ab90 (LWP 15923)] [New Thread 0xb074bb90 (LWP 15886)] [New Thread 0xb0f4cb90 (LWP 15885)] [New Thread 0xb174db90 (LWP 15884)] [New Thread 0xb283bb90 (LWP 15881)] [New Thread 0xb5a57b90 (LWP 15880)] 0xb80c6424 in __kernel_vsyscall ()
+ Trace 218176
Thread 1 (Thread 0xb6b09980 (LWP 15879))
----------- .xsession-errors (600039 sec old) --------------------- (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead (epiphany-browser:15080): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
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 bug 596308 ***