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 775632 - crash when accessing dictionary.cambridge.org
crash when accessing dictionary.cambridge.org
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: General
3.22.x (obsolete)
Other Linux
: High normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-05 12:40 UTC by andreas
Modified: 2016-12-06 20:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description andreas 2016-12-05 12:40:49 UTC
I tried several time to access dictionary.cambridge.org and epiphany crashed. I got this message:

The site at http://dictionary.cambridge.org/ may have caused Web to close unexpectedly.
Comment 1 andreas 2016-12-05 12:54:50 UTC
I use fedora 25.
Comment 2 Michael Catanzaro 2016-12-05 14:08:22 UTC
Hm, it works for me with epiphany-1:3.22.3-1.fc25, webkitgtk4-2.14.2-1.fc25.

Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!

The stack trace needs to be obtained from the WebKitWebProcess that is crashing, not the epiphany process itself.
Comment 3 Michael Catanzaro 2016-12-05 14:09:13 UTC
Note that the easiest way to get a stack trace would just be to report the issue to Red Hat Bugzilla using Fedora's Problem Reporting tool, then post a link to the Red Hat Bugzilla issue here.
Comment 4 andreas 2016-12-06 09:23:41 UTC
I have reported the issue to Red Hat Bugzilla. Here is the link:
https://bugzilla.redhat.com/show_bug.cgi?id=1401851
Comment 5 andreas 2016-12-06 12:33:15 UTC


Thread 1 (Thread 0x7fa57dbe9ac0 (LWP 13509))

  • #0 _XReply
    at xcb_io.c line 566
  • #1 _XGetWindowAttributes
    at GetWAttrs.c line 115
  • #2 XGetWindowAttributes
    at GetWAttrs.c line 150
  • #3 gtk_socket_realize
    at gtksocket.c line 420
  • #4 _g_closure_invoke_va
    at gclosure.c line 867
  • #5 g_signal_emit_valist
    at gsignal.c line 3300
  • #6 g_signal_emit
    at gsignal.c line 3447
  • #7 gtk_widget_realize
    at gtkwidget.c line 5456
  • #8 gtk_widget_set_parent
    at gtkwidget.c line 9568
  • #9 webkitWebViewBaseContainerAdd
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/UIProcess/API/gtk/WebKitWebViewBase.cpp line 425
  • #10 g_cclosure_marshal_VOID__OBJECTv
    at gmarshal.c line 2102
  • #11 _g_closure_invoke_va
    at gclosure.c line 867
  • #12 g_signal_emit_valist
    at gsignal.c line 3300
  • #13 g_signal_emit
    at gsignal.c line 3447
  • #14 gtk_container_add
    at gtkcontainer.c line 1875
  • #15 WebKit::WebPageProxy::createPluginContainer
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/UIProcess/gtk/WebPageProxyGtk.cpp line 107
  • #16 IPC::callMemberFunctionImpl<WebKit::WebPageProxy, void
  • #19 WebKit::WebPageProxy::didReceiveSyncMessage
    at /usr/src/debug/webkitgtk-2.14.2/x86_64-redhat-linux-gnu/DerivedSources/WebKit2/WebPageProxyMessageReceiver.cpp line 1457
  • #20 IPC::MessageReceiverMap::dispatchSyncMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/Platform/IPC/MessageReceiverMap.cpp line 140
  • #21 WebKit::ChildProcessProxy::dispatchSyncMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/UIProcess/ChildProcessProxy.cpp line 157
  • #22 WebKit::WebProcessProxy::didReceiveSyncMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/UIProcess/WebProcessProxy.cpp line 514
  • #23 IPC::Connection::dispatchSyncMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/Platform/IPC/Connection.cpp line 789
  • #24 IPC::Connection::dispatchMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/Platform/IPC/Connection.cpp line 856
  • #25 IPC::Connection::dispatchOneMessage
    at /usr/src/debug/webkitgtk-2.14.2/Source/WebKit2/Platform/IPC/Connection.cpp line 889
  • #26 WTF::Function<void
  • #27 WTF::RunLoop::performWork
    at /usr/src/debug/webkitgtk-2.14.2/Source/WTF/wtf/RunLoop.cpp line 105
  • #28 WTF::RunLoop::<lambda(gpointer)>::operator()
    at /usr/src/debug/webkitgtk-2.14.2/Source/WTF/wtf/glib/RunLoopGLib.cpp line 66
  • #29 WTF::RunLoop::<lambda(gpointer)>::_FUN(gpointer)
    at /usr/src/debug/webkitgtk-2.14.2/Source/WTF/wtf/glib/RunLoopGLib.cpp line 68
  • #30 g_main_dispatch
    at gmain.c line 3203
  • #31 g_main_context_dispatch
    at gmain.c line 3856
  • #32 g_main_context_iterate
    at gmain.c line 3929
  • #33 g_main_context_iteration
    at gmain.c line 3990
  • #34 g_application_run
    at gapplication.c line 2381
  • #35 main
    at ephy-main.c line 495

Comment 6 Michael Catanzaro 2016-12-06 16:00:46 UTC
OK, it's a WebKit bug, but the bug is triggered by some browser plugin on your computer, that's why I can't reproduce it. What plugins do you have installed?
Comment 7 andreas 2016-12-06 20:56:32 UTC
I have installed the flash plugin.