GNOME Bugzilla – Bug 382922
crash after closing epiphany when it was displaying a website
Last modified: 2006-12-11 13:38:00 UTC
Distribution: Debian 4.0 Package: epiphany Severity: trivial Version: GNOME2.14.3 2.14.x Gnome-Distributor: Debian Synopsis: crash after closing epiphany when it was displaying a website Bugzilla-Product: epiphany Bugzilla-Component: General Bugzilla-Version: 2.14.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: epiphany crashed when display a map at www.mappy.fr Steps to reproduce the crash: 1. go to www.mappy.fr 2. do a map search, and move it with the controls located at the left side of the map 3. close the browser Expected Results: crash How often does this happen? randomly Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/epiphany-browser' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1240688960 (LWP 15845)] (no debugging symbols found) 0xb70a3231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 91991
Thread 1 (Thread -1240688960 (LWP 15845))
------- Bug created by bug-buddy at 2006-12-06 08:33 -------
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? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hello, Here's the backtrace I got when running through the steps to reproduce the crash. Unfortunately I could not repeat it more than once with the (supposed to be) non stripped version of the browser. I followed the instructions at http://wiki.debian.org/HowToGetABacktrace but I did not get any info from gdb as the program exited normaly. Then I just ran it again and then I got: Backtrace was generated from '/usr/libexec/epiphany-browser' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241508160 (LWP 8062)] 0xb6fdb231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 92814
Thread 1 (Thread -1241508160 (LWP 8062))
from bug-buddy. I got this only once. From then the browser seems to act normally. What has changed since the first crash is that I upgraded my Debian workstation with the latest updates which includes flashplugin beta9 and the new recompiled version of epiphany I'm now using just in case the crash occurs again. Sorry I'm no programmer, hope this helps.
Hi, could you please also install debug packages voor GTK, Glib, and xulrunner? Your backtrace only shows debug symbols for epiphany itself. Also, try upgrading to a newer epiphany version (2.16.x) to see if the problem still occurs. Thanks!
Hello, Ok I'm on my way to install unstripped versions of these libs. I just wanted to point out that I'm afraid I will not be able to install 2.16 version of the browser as it would compel me to stop sticking to Debian Etch, which is known to be the next so called stable version (soon, I hope). As a matter of fact I first upgraded to Etch because I thought it would be a good balance between the most recent version of Gnome desktop (among other softwares) and system stability, giving the fact that I don't use it for "testing". For now I'm quite satisfied with my choice. I don't really want to see more weird things happen with Sid (which include 2.16) installed. So I wondered if recompiling epiphany 2.16 from source would do the trick, which I suppose would also raise some dependency problems. I'm asking you if it's a good or a bad idea before I run into trouble :-). Feel free to tell me about it and I could eventually recompile epiphany...or find another way to help you out! Please I beg you to keep in mind that whatever you ask me to do, I'd rather do it over Debian Etch distribution. Thanks for your help and interest... Jack H.
If you can provide a full backtrace with the 2.14 release you're using, it would be a good start. You could try jhbuild for a more recent epiphany version built from source. Thanks!
Created attachment 78109 [details] backtrace from epiphany crash
Comment on attachment 78109 [details] backtrace from epiphany crash Hello, Here the new backtrace I got from the crash with libxul0d-dbg, libgtk2.0-0-dbg and libglib2.0-0-dbg installed. All these symbols really have no meaning to me. Hope I didn't miss anything. btw epiphany seems to act much better since I recompiled it, as it took me a couple of more tries to get the crash. I'm now planning on trying it with 2.16.x version soon. Jack H.
*** This bug has been marked as a duplicate of 349051 ***