GNOME Bugzilla – Bug 419714
crash in Epiphany Web Browser: Visiting http://www.stan...
Last modified: 2007-05-27 11:07:11 UTC
Version: 2.18.0 What were you doing when the application crashed? Visiting http://www.standaard.be Distribution: Mandriva Linux release 2007.1 (Cooker) for x86_64 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.20.1-tmb-desktop-4mdv #1 Tue Mar 6 22:43:56 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-Quicksilver Icon Theme: Clearlooks Memory status: size: 544776192 vsize: 544776192 resident: 67387392 share: 25186304 rss: 67387392 rss_rlim: 18446744073709551615 CPU usage: start_time: 1174220351 rtime: 9843 utime: 9245 stime: 598 cutime:816 cstime: 139 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47389559946816 (LWP 13909)] [New Thread 1124096320 (LWP 5899)] [New Thread 1115703616 (LWP 5898)] [New Thread 1107310912 (LWP 5897)] [New Thread 1098918208 (LWP 1517)] [New Thread 1140881728 (LWP 1516)] [New Thread 1090525504 (LWP 13931)] [New Thread 1082132800 (LWP 13916)] (no debugging symbols found) 0x00002b19bacffc2e in waitpid () from /lib64/libpthread.so.0
+ Trace 119702
Thread 1 (Thread 47389559946816 (LWP 13909))
----------- .xsession-errors (2519 sec old) --------------------- <result uri="man:pamtohtmltbl(1)" title="pamtohtmltbl manual page"> <snippet>convert pnm/pam visual image to an HTML table</snippet> <score>0.1</score> </result> <result uri="man:pamtojpeg2k(1)" title="pamtojpeg2k manual page"> <snippet>convert PAM/PNM image to a JPEG-2000 code stream</snippet> <score>0.1</score> </result> <result uri="man:pamtopfm(1)" title="pamtopfm manual page"> <snippet>Convert Netpbm image to PFM (Portable Float Map)</snippet> <score>0.1</score> </result> <result uri="man:pamtopfm(1)" title="pamtopfm manual page"> <sni ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Thanks in advance! Since you're running Mandriva Cooker, you should be able to urpmi mozilla-firefox-debug, epiphany-debug, gtk+2.0-debug, glib2.0-debug quite easily.
OK, Epiphany crashed again right now with the debug packages installed. I'm not sure if it is the same crash though. I have the impression that it is x86_64 specific: I had already three crashes in about two hours on x86_64, so it's not too hard to hit, but I haven't seen Epiphany crashes in i586. This crash happened when I was downloading a tar.gz from http://art4linux.org/pages/wallpapers10.html (actually I was in the GTK+ file chooser dialog selecting a location where to save the file).
Created attachment 84823 [details] Complete backtrace
Looks like a problem in gnome-vfs. Could you install gnome-vfs2-debug as well? Thanks!
Created attachment 84845 [details] Another backtrace Here's a new backtrace. I have the impression that the previous backtrace was about another bug, triggered when downloading a file, and that this is the same as the first one, triggered when visiting a site (it was http://www.donna.be this time. I wanted to visit this site as I know it uses Flash, and I had the impression that Flash suddenly was not working anymore on other sites. As I'm using x86_64 I'm wondering if the suddenly not working Flash could be the same as bug #407419).
I don't believe the trace from attachment 84845 [details] is the same problem as the crash that sparked this report. On the face of it I'd say that the trace from comment #5 is a plugin unload timeout in the Flash plugin (bug 349051).
Frederik, are you able to reproduce this?
I do not plan trying to reproduce this crash anymore, so I guess it can be closed...
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!