GNOME Bugzilla – Bug 618279
crash in Epiphany Web Bookmarks: Failure loading web page
Last modified: 2010-05-13 14:17:10 UTC
Version: 2.30.2 What were you doing when the application crashed? Failure loading web page Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.30.0 2010-05-09 (Gentoo) BugBuddy Version: 2.30.0 System: Linux 2.6.34-rc7 #199 SMP Mon May 10 07:54:51 EEST 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10800000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Compact Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 712306688 vsize: 712306688 resident: 112275456 share: 29020160 rss: 112275456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273505935 rtime: 375 utime: 332 stime: 43 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2400.1-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [Thread debugging using libthread_db enabled] [New Thread 0x7f6579673710 (LWP 25738)] [New Thread 0x7f6579f74710 (LWP 25737)] 0x00007f659062acdd in __libc_waitpid (pid=27720, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 221845
Thread 1 (Thread 0x7f65963258c0 (LWP 24679))
Inferior 1 [process 24679] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib **: gmem.c:137: failed to allocate 186762357903461 bytes GLib-ERROR **: gmem.c:137: failed to allocate 10421875554064360889 bytes aborting...
This appears to be a problem somewhere in the favicon cache.
related to bug 604993 ?
Fridrich pointed out this changeset in Gtk+: http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-20&id=a0f23e1706b34bca6a65183040d1f1498cce2a50
*** This bug has been marked as a duplicate of bug 617878 ***