GNOME Bugzilla – Bug 542608
crash in Epiphany Web Browser:
Last modified: 2008-07-12 09:59:02 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 518684672 vsize: 518684672 resident: 67616768 share: 28110848 rss: 67616768 rss_rlim: 18446744073709551615 CPU usage: start_time: 1215829771 rtime: 180 utime: 158 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b441163e140 (LWP 7136)] [New Thread 0x44808950 (LWP 7160)] [New Thread 0x43806950 (LWP 7151)] [New Thread 0x43005950 (LWP 7145)] [New Thread 0x42003950 (LWP 7142)] [New Thread 0x41001950 (LWP 7141)] [New Thread 0x41802950 (LWP 7140)] [New Thread 0x40800950 (LWP 7137)] (no debugging symbols found) 0x00002b440cd9dedf in waitpid () from /lib/libpthread.so.0
+ Trace 202606
Thread 1 (Thread 0x2b441163e140 (LWP 7136))
----------- .xsession-errors (115 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) --------------------------------------------------
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 537495 ***