GNOME Bugzilla – Bug 562906
crash in Epiphany Web Browser:
Last modified: 2008-12-01 21:50:52 UTC
Version: 2.24.1 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Nov 8 19:00:26 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 191324160 vsize: 191324160 resident: 86462464 share: 29560832 rss: 86462464 rss_rlim: 4294967295 CPU usage: start_time: 1228161441 rtime: 13446 utime: 12135 stime: 1311 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' [Thread debugging using libthread_db enabled] [New Thread 0xb6976700 (LWP 3757)] [New Thread 0xaecedb90 (LWP 6403)] [New Thread 0xb175cb90 (LWP 6380)] [New Thread 0xb2003b90 (LWP 3792)] [New Thread 0xb3927b90 (LWP 3787)] [New Thread 0xb50f9b90 (LWP 3786)] [New Thread 0xb48f8b90 (LWP 3783)] [New Thread 0xb5901b90 (LWP 3762)] 0xb7f3b424 in __kernel_vsyscall ()
+ Trace 210395
Thread 1 (Thread 0xb6976700 (LWP 3757))
----------- .xsession-errors (22 sec old) --------------------- (xchat:3641): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat:3641): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat:3641): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat:3641): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat:3641): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed warning: (Internal error: pc 0xb64637b4 in read in psymtab, but not in symtab.) warning: (Internal error: pc 0xb646379c in read in psymtab, but not in symtab.) warning: (Internal error: pc 0xb64637b4 in read in psymtab, but not in symtab.) --------------------------------------------------
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 561372 ***