GNOME Bugzilla – Bug 576258
crash in Epiphany Web Browser: Just browsing.
Last modified: 2009-09-26 04:55:26 UTC
Version: 2.27.1 What were you doing when the application crashed? Just browsing. Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.26.0 2009-03-20 (Gentoo) BugBuddy Version: 2.26.0 System: Linux 2.6.28 #134 SMP PREEMPT Sat Dec 27 13:16:10 EET 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Compact Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 577986560 vsize: 577986560 resident: 115380224 share: 26566656 rss: 115380224 rss_rlim: 18446744073709551615 CPU usage: start_time: 1237700564 rtime: 5322 utime: 4961 stime: 361 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7fd41970c760 (LWP 19576)] 0x00007fd414adf55f in __libc_waitpid (pid=19984, stat_loc=0x7fff2174b630, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 213706
Thread 1 (Thread 0x7fd41970c760 (LWP 19576))
---- Critical and fatal warnings logged during execution ---- ** Gdk **: gdk_window_new: assertion `window != NULL' failed ** Gdk **: gdk_window_set_user_data: assertion `GDK_IS_WINDOW (window)' failed ** Gdk **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** Gdk **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
=> WebKit
Seems to be crashing because there's no colormap set, but the code in gtkstyle.c does not check for that. Not sure why there would be no colormap set. Moving to GTK+, since it seems that at least we should protect against this case here?
This is a dup of *** This bug has been marked as a duplicate of 353503 ***
*** Bug 581267 has been marked as a duplicate of this bug. ***
Christian, are you sure it's a duplicate? This bug happens with the webkit backend.
*** Bug 596398 has been marked as a duplicate of this bug. ***