GNOME Bugzilla – Bug 539917
crash in Epiphany Web Browser: increased the size of te...
Last modified: 2010-03-19 12:21:20 UTC
Version: 2.22.2 What were you doing when the application crashed? increased the size of text Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-rc6 #2 SMP Fri Jun 13 11:14:18 BST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 779227136 vsize: 779227136 resident: 162541568 share: 35524608 rss: 162541568 rss_rlim: 18446744073709551615 CPU usage: start_time: 1214211816 rtime: 35648 utime: 33284 stime: 2364 cutime:10089 cstime: 868 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7fdb939a6780 (LWP 24011)] [New Thread 0x421af950 (LWP 20938)] [New Thread 0x44e4e950 (LWP 20934)] [New Thread 0x43e4c950 (LWP 15243)] [New Thread 0x4464d950 (LWP 24053)] [New Thread 0x4364b950 (LWP 24019)] [New Thread 0x419ae950 (LWP 24018)] [New Thread 0x42e4a950 (LWP 24017)] 0x00007fdb8c28fedf in waitpid () from /lib/libpthread.so.0
+ Trace 201243
----------- .xsession-errors (416 sec old) --------------------- ** (update-notifier:4317): WARNING **: no cdrom: disk gnome-mount 0.7 Unmounted /dev/sdb1 (gnome-terminal:12021): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-panel:4296): GWeather-WARNING **: Failed to get METAR data. ** Message: <info> You are now connected to the wired network. (gnome-terminal:12021): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x342cab9 (swordsman ); these messages lack timestamps and therefore suck. --------------------------------------------------
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 525357 ***
I don't see the similarity between the stack trace here and that of bug #525357
Hmm, possibly the Simple Dupe Finder tricked me.
in the #525357 the stacktrace is more completely thant here... and here i don't see the crash... i think... missing information or a bad stacktrace...
I've not seen this for ages and it was with the gecko backend.