Description of problem: 1. Opened the web application 2. Searched for "Chip donanım test" in google 3. Opened two new tabs from the search results: http://www.chip.com.tr/donanim/ and http://www.chip.com.tr/inceleme/ 4. Web crashed. Version-Release number of selected component: epiphany-runtime-3.22.1-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: epiphany crash_function: XGetWindowAttributes executable: /usr/bin/epiphany global_pid: 2153 kernel: 4.8.6-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 XGetWindowAttributes at GetWAttrs.c:150 #3 gtk_socket_realize at gtksocket.c:420 #4 _g_closure_invoke_va at gclosure.c:867 #7 gtk_widget_realize at gtkwidget.c:5454 #8 gtk_widget_set_parent at gtkwidget.c:9566 #9 webkitWebViewBaseContainerAdd(GtkContainer*, GtkWidget*) at /usr/src/debug/webkitgtk-2.14.1/Source/WebKit2/UIProcess/API/gtk/WebKitWebViewBase.cpp:421 #10 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #11 _g_closure_invoke_va at gclosure.c:867 #14 gtk_container_add at gtkcontainer.c:1875 #15 WebKit::WebPageProxy::createPluginContainer(unsigned long&) at /usr/src/debug/webkitgtk-2.14.1/Source/WebKit2/UIProcess/gtk/WebPageProxyGtk.cpp:107 Potential duplicate: bug 1248230
Created attachment 1220892 [details] File: backtrace
Created attachment 1220893 [details] File: cgroup
Created attachment 1220894 [details] File: core_backtrace
Created attachment 1220895 [details] File: dso_list
Created attachment 1220896 [details] File: environ
Created attachment 1220897 [details] File: exploitable
Created attachment 1220898 [details] File: limits
Created attachment 1220899 [details] File: maps
Created attachment 1220900 [details] File: mountinfo
Created attachment 1220901 [details] File: namespaces
Created attachment 1220902 [details] File: open_fds
Created attachment 1220903 [details] File: proc_pid_status
Created attachment 1220904 [details] File: var_log_messages
Muhammet, were you running under Wayland or X11?
(In reply to Michael Catanzaro from comment #14) > Muhammet, were you running under Wayland or X11? It was under Wayland.
OK, thanks. It upstreamed as WebKit #164910.
Hi Muhammet, are you able to reproduce this crash? The backtrace is rather confusing, so if you are able to reproduce it then that would be helpful to know.
*** Bug 1399921 has been marked as a duplicate of this bug. ***
(In reply to Michael Catanzaro from comment #17) > Hi Muhammet, are you able to reproduce this crash? The backtrace is rather > confusing, so if you are able to reproduce it then that would be helpful to > know. Hi Michael, Yes, I have switched to Wayland session, and reproduced the crash several times. Sometimes it crashed when I clicked the link to go to the next page of the website article, but mostly it crashed as soon as the page was loaded.
OK, last question. Do you know what browser plugin that website is trying to load? This might be hard to check. The plugin process is not crashing so we don't know from this bug report, but the plugin process should not be doing that in Wayland. This bug is a bit tricky because the problem is somewhere in the plugin process and that problem is causing the UI process to crash. We should of course make the UI process not crash, but that won't fix the real problem here.
*** Bug 1401851 has been marked as a duplicate of this bug. ***