After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 539182 - crash in Epiphany Web Browser: Visiting a website. Note...
crash in Epiphany Web Browser: Visiting a website. Note...
Status: RESOLVED DUPLICATE of bug 535883
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-19 20:30 UTC by deleriux
Modified: 2008-06-20 10:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description deleriux 2008-06-19 20:30:16 UTC
Version: 2.22.2

What were you doing when the application crashed?
Visiting a website. Note this has occured since updating my packages.

Attached is a list of updated applications.

Jun 19 16:55:52 Updated: devhelp-0.19.1-1.fc9.x86_64
Jun 19 16:55:58 Updated: 1:NetworkManager-0.7.0-0.9.4.svn3675.fc9.x86_64
Jun 19 16:55:59 Updated: 1:NetworkManager-gnome-0.7.0-0.9.4.svn3675.fc9.x86_64
Jun 19 16:56:01 Updated: 2:tar-1.19-4.fc9.x86_64
Jun 19 16:56:15 Updated: xulrunner-devel-1.9-1.fc9.x86_64
Jun 19 16:56:15 Updated: policycoreutils-newrole-2.0.49-3.fc9.x86_64
Jun 19 16:56:16 Updated: alsa-utils-1.0.16-3.fc9.x86_64
Jun 19 16:56:17 Updated: rsyslog-3.16.1-2.fc9.x86_64
Jun 19 16:56:19 Updated: 5:mutt-1.5.18-2.fc9.x86_64
Jun 19 16:56:20 Updated: gnome-python2-desktop-2.22.0-4.fc9.x86_64
Jun 19 16:56:22 Updated: evolution-data-server-doc-2.22.2-1.fc9.x86_64
Jun 19 16:56:22 Updated: gnome-python2-applet-2.22.0-4.fc9.x86_64
Jun 19 16:56:22 Updated: gnome-python2-gnomeprint-2.22.0-4.fc9.x86_64
Jun 19 16:56:23 Updated: gnome-python2-gnomekeyring-2.22.0-4.fc9.x86_64
Jun 19 16:56:24 Updated: evolution-data-server-devel-2.22.2-1.fc9.x86_64
Jun 19 16:56:25 Updated: policycoreutils-gui-2.0.49-3.fc9.x86_64
Jun 19 16:56:29 Updated: firefox-3.0-1.fc9.x86_64
Jun 19 16:56:30 Updated: freetype-2.3.5-6.fc9.i386
Jun 19 16:56:30 Updated: freetype-devel-2.3.5-6.fc9.i386
Jun 19 16:56:31 Updated: freetype-devel-2.3.5-6.fc9.x86_64



Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.6-55.fc9.x86_64 #1 SMP Tue Jun 10 16:05:21 EDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10499902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Cillop-Go
Icon Theme: gnome

Memory status: size: 550793216 vsize: 550793216 resident: 46243840 share: 25632768 rss: 46243840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213907237 rtime: 78 utime: 73 stime: 5 cutime:2 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f1e618d27b0 (LWP 6224)]
[New Thread 0x453bb950 (LWP 6237)]
[New Thread 0x449ba950 (LWP 6236)]
[New Thread 0x43fb9950 (LWP 6235)]
[New Thread 0x435b8950 (LWP 6234)]
[New Thread 0x42bb7950 (LWP 6233)]
[New Thread 0x413a9950 (LWP 6232)]
[New Thread 0x421b6950 (LWP 6231)]
0x0000003aa8c0e86f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 0x7f1e618d27b0 (LWP 6224))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #6 <signal handler called>
  • #7 EphyDOMLinkEventListener::HandleEvent
    at EphyBrowser.cpp line 370
  • #8 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #10 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #11 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #12 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #13 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #14 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #15 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #16 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #17 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #18 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #19 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #20 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #21 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #22 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #23 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #24 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #25 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #26 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #27 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #28 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #29 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #30 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #31 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #32 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #33 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #34 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #35 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #36 ??
    from /usr/lib64/xulrunner-1.9/libxul.so
  • #37 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #38 ??
    from /lib64/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #40 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #41 main
    at ephy-main.c line 731


----------- .xsession-errors (6 sec old) ---------------------
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory
which: no soundwrapper in (/home/matthew/.bin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin)
which: no soundwrapper in (/home/matthew/.bin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin)
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory
** (epiphany:6021): WARNING **: EphyBrowser initialization failed for 0x1cc6160
(gnome-terminal:6127): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** (epiphany:6192): WARNING **: EphyBrowser initialization failed for 0xbf3170
** (epiphany:6224): WARNING **: EphyBrowser initialization failed for 0x9eb170
--------------------------------------------------
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2008-06-19 22:21:06 UTC
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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Peter Bloomfield 2008-06-19 22:30:08 UTC
FWIW: Ephy was doing the same for me, on about every site I tried to visit.  Gdb gave a similar stack trace, and since it was deep in xulrunner and xulrunner was upgraded this morning, I downgraded it to the F9 release version.  Ephy hasn't crashed since.
Comment 3 deleriux 2008-06-19 23:47:44 UTC
This is a similar crash that occured I have the coredump for.

This is the backgrace with debugging symbols included.

  • #0 raise
    from /lib64/libpthread.so.0
  • #1 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 212
  • #2 <signal handler called>
  • #3 EphyDOMLinkEventListener::HandleEvent
    at EphyBrowser.cpp line 370
  • #4 nsEventListenerManager::HandleEventSubType
    at nsEventListenerManager.cpp line 1080
  • #5 nsEventListenerManager::HandleEvent
    at nsEventListenerManager.cpp line 1184
  • #6 nsEventTargetChainItem::HandleEvent
    at nsEventDispatcher.cpp line 210
  • #7 nsEventTargetChainItem::HandleEventTargetChain
    at nsEventDispatcher.cpp line 291
  • #8 nsEventDispatcher::Dispatch
  • #9 nsEventDispatcher::DispatchDOMEvent
    at nsEventDispatcher.cpp line 541
  • #10 nsEventListenerManager::DispatchEvent
    at nsEventListenerManager.cpp line 1309
  • #11 nsDOMEventRTTearoff::DispatchEvent
    at nsGenericElement.cpp line 1092
  • #12 nsPLDOMEvent::Run
    at nsPLDOMEvent.cpp line 71
  • #13 nsContentUtils::RemoveScriptBlocker
    at nsContentUtils.cpp line 4221
  • #14 ~mozAutoDocUpdate
    at ../../../dist/include/content/mozAutoDocUpdate.h line 72
  • #15 nsGenericElement::doInsertChildAt
    at nsGenericElement.cpp line 2765
  • #16 HTMLContentSink::ProcessLINKTag
  • #17 CNavDTD::AddHeadContent
    at CNavDTD.cpp line 3074
  • #18 CNavDTD::HandleStartToken
    at CNavDTD.cpp line 1434
  • #19 CNavDTD::HandleToken
    at CNavDTD.cpp line 760
  • #20 CNavDTD::BuildModel
    at CNavDTD.cpp line 336
  • #21 nsParser::BuildModel
    at nsParser.cpp line 1773
  • #22 nsParser::ResumeParse
    at nsParser.cpp line 1650
  • #23 nsParser::OnDataAvailable
    at nsParser.cpp line 2287
  • #24 nsStreamListenerTee::OnDataAvailable
    at nsStreamListenerTee.cpp line 97
  • #25 nsHttpChannel::OnDataAvailable
  • #26 nsInputStreamPump::OnStateTransfer
    at nsInputStreamPump.cpp line 508
  • #27 nsInputStreamPump::OnInputStreamReady
    at nsInputStreamPump.cpp line 398
  • #28 nsInputStreamReadyEvent::Run
    at nsStreamUtils.cpp line 111
  • #29 nsThread::ProcessNextEvent
    at nsThread.cpp line 510
  • #30 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #31 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #32 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #33 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #34 ??
    from /lib64/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 main
    at ephy-main.c:731


I appreciate Peters workaround (I had a feeling it was to do with xulrunner as there was a german post I googled that brought it up) but this then breaks Firefox which is used by other people on my system.
Comment 4 deleriux 2008-06-20 09:01:19 UTC
Assume I must reopen this bug in order for someone to notice the stack trace. I apologize if this is not the case.
Comment 5 Cosimo Cecchi 2008-06-20 10:23:55 UTC
Thanks, I found this has already been reported in another bug. Closing as a duplicate.

*** This bug has been marked as a duplicate of 535883 ***