Bug 1551610 - epiphany (WebKit) hangs with 99% cpu for certain web pages
Summary: epiphany (WebKit) hangs with 99% cpu for certain web pages
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: webkitgtk4
Version: 27
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Popela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-05 14:11 UTC by Don Swaner
Modified: 2018-03-07 15:44 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-07 15:44:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
WebKit Project 183406 0 None None None 2018-03-07 15:32:49 UTC

Description Don Swaner 2018-03-05 14:11:29 UTC
Description of problem:
For some Amazon web pages, epiphany hangs, with WebKitWebProces using 99% cpu.

Version-Release number of selected component (if applicable):
epiphany-runtime-3.26.5.1-1.fc27.x86_64
webkitgtk4-2.18.6-1.fc27.x86_64

How reproducible:
very, but not 100%

Steps to Reproduce:
1.  In epiphany, open https://www.amazon.com/Ingathering-Complete-People-Stories-Henderson/dp/0915368587/ref=sr_1_cc_1?s=aps&ie=UTF8&qid=1520257317&sr=1-1-catcorr&keywords=ingathering

Actual results:
epiphany hangs.  "top" command shows 99% cpu for WebKitWebProces

Expected results:
Web page loads OK.

Additional info:
Since the Amazon web pages are dynamic, with changing advertisements and recommendations, tracking down the problem may be challenging.  Quitting epiphany takes about 20 seconds.  In ~/.config/epiphany, deleting session_state.xml and renaming session_state.xml~ gives an error display and allows you to continue using ephiphany, which otherwise keeps trying to load the bad web page when epiphany is restarted.  Another page which causes the same problem is:
https://www.amazon.com/Dragons-Egg-Dragon-Eggs-Book-ebook/dp/B01JOL7BKC/ref=sr_1_1?s=digital-text&ie=UTF8&qid=1520258748&sr=1-1&keywords=dragon%27s+egg+Sorensen

Comment 1 Michael Catanzaro 2018-03-05 14:20:51 UTC
Does it work if you run with the environment variable WEBKIT_DISABLE_COMPOSITING_MODE=1?

Comment 2 Don Swaner 2018-03-05 16:10:28 UTC
(In reply to Michael Catanzaro from comment #1)
> Does it work if you run with the environment variable
> WEBKIT_DISABLE_COMPOSITING_MODE=1?

No. Same result.

Comment 3 Michael Catanzaro 2018-03-05 16:33:07 UTC
OK, so it's not a GPU problem... strange that I can't reproduce. I tried disabling the adblocker too; still can't reproduce.

Next step is to move this to the upstream bugtracker. Here's my canned reply for that:

This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.

Comment 4 Don Swaner 2018-03-05 17:03:00 UTC
I have the epiphany addblocker disabled.  Unfortunately, the Amazon web page will display some previous browsing selections and some recommendations, which will depend on my unique Amazon browsing history, so that this problem may be difficult or impossible to replicate.

Comment 5 Don Swaner 2018-03-06 22:36:54 UTC
If I turn ad blocking on, then both URL's load OK.  Plugins are enabled, but I haven't explicitly installed any.

On the second URL, which had successfully loaded, I turned ad blocking off, and reloaded the page, and it hung again.

So, it would appear that the problem is caused by some Amazon ads, but not other ads.

Comment 6 Michael Catanzaro 2018-03-07 00:52:47 UTC
This will be a nightmare to track down, since the ads will be based on your location and browsing habits... still, I've heard of ads freezing WebKit before, so it's not just a problem for you. I don't think we have a bug report for it yet, though. Best option, if you care to create another Bugzilla account, is to report it upstream:

(In reply to Michael Catanzaro from comment #3) 
> This issue is most likely a bug in WebKit. Please report the bug to
> https://bugs.webkit.org/ including a link to this bug report and noting the
> version of WebKitGTK+ that you have installed. When reporting the WebKit
> bug, be sure to include the prefix '[GTK]' in the bug summary and select the
> 'WebKit Gtk' component.

Comment 7 Michael Catanzaro 2018-03-07 15:44:20 UTC
OK, thanks for reporting upstream! It's more likely to be fixed there.


Note You need to log in before you can comment on or make changes to this bug.