GNOME Bugzilla – Bug 352705
crash in Epiphany Web Bookmarks: Clicked on a link at www...
Last modified: 2007-04-09 13:46:00 UTC
Version: 2.15.91 What were you doing when the application crashed? Clicked on a link at www.aftonbladet.se. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 187437056 vsize: 0 resident: 187437056 share: 0 rss: 62410752 rss_rlim: 0 CPU usage: start_time: 1156437728 rtime: 0 utime: 6167 stime: 0 cutime:5872 cstime: 0 timeout: 295 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228364112 (LWP 14279)] [New Thread -1343886432 (LWP 15701)] [New Thread -1308021856 (LWP 15700)] [New Thread -1382896736 (LWP 15699)] [New Thread -1335493728 (LWP 15698)] [New Thread -1326965856 (LWP 15697)] [New Thread -1318061152 (LWP 14299)] [New Thread -1299629152 (LWP 14298)] [New Thread -1273414752 (LWP 14286)] [New Thread -1265022048 (LWP 14285)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70931
Thread 1 (Thread -1228364112 (LWP 14279))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
It was a random crash. Can't reproduce it again. Sorry.
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. Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report? Matches the stacktrace in bug 353007, which is a duplicate of bug 349051. *** This bug has been marked as a duplicate of 349051 ***
*** Bug 410552 has been marked as a duplicate of this bug. ***
*** Bug 411283 has been marked as a duplicate of this bug. ***
*** Bug 427674 has been marked as a duplicate of this bug. ***