Bug 165998

Summary: [GTK] Slowness and crashes when loading some web pages on Intel NUC
Product: WebKit Reporter: Aram J. Agajanian <agajan>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Major CC: agajan, bugs-noreply, mcatanzaro
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   
See Also: https://bugzilla.gnome.org/show_bug.cgi?id=776197
Attachments:
Description Flags
Output of glxinfo command on Intel NUC6I5SYK.
none
Console output when running epiphany from the command line none

Aram J. Agajanian
Reported 2016-12-17 11:33:02 PST
I have been using WebkitGtk+ as part of the Epiphany web browser in Fedora Linux. My work computer has a Radeon video card and it works well. I have another computer which is an Intel NUC (NUC6I5SYK). On that computer, there is slowness and crashes when loading some web pages. The build of WebkitGtk+ is webkitgtk4-2.14.2-1.fc25.x86_64.
Attachments
Output of glxinfo command on Intel NUC6I5SYK. (25.18 KB, text/plain)
2016-12-17 11:35 PST, Aram J. Agajanian 		no flags
Details
Console output when running epiphany from the command line (12.92 KB, text/plain)
2016-12-17 12:01 PST, Aram J. Agajanian 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Aram J. Agajanian
Comment 1 2016-12-17 11:35:32 PST
Created attachment 297411 [details] Output of glxinfo command on Intel NUC6I5SYK.
Aram J. Agajanian
Comment 2 2016-12-17 11:46:16 PST
The issues of slowness and crashing persist when running Epiphany with the following command: WEBKIT_DISABLE_COMPOSITING_MODE=1 epiphany
Aram J. Agajanian
Comment 3 2016-12-17 12:01:41 PST
Created attachment 297412 [details] Console output when running epiphany from the command line It took a while but I got it to crash. Not sure if the crash is caused by me continuously making mouse clicks while the program appears to be frozen. Some web pages (lwn.net) don't seem to have any slowness issues. Other pages (Google Search, Amazon.com) seem to have these issues regularly.
Michael Catanzaro
Comment 4 2016-12-17 15:23:12 PST
Oooh, lots of badness in that log. I wonder what the 256 exit status from WebKitPluginProcess means. Could you get a backtrace for the first critical warning? You'll need to run with G_DEBUG=fatal-criticals in the environment to make it crash on the first critical. See [1] for help on getting traces and keep in mind the criticals may be in a secondary process rather than the main Epiphany process. [1] http://fedoraproject.org/wiki/StackTraces
Note You need to log in before you can comment on or make changes to this bug.