Bug 1296784 - Viewing Webpage (Viral Page via Facebook) Locks Entire Computer
Summary: Viewing Webpage (Viral Page via Facebook) Locks Entire Computer
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: webkitgtk4
Version: 23
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Popela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-08 03:05 UTC by Justin Haygood
Modified: 2016-03-01 23:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-01 23:57:19 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
WebKit Project 126122 0 None None None 2016-03-01 23:57:19 UTC

Description Justin Haygood 2016-01-08 03:05:29 UTC 
Description of problem:

Going to http://storycrash.com/this-man-came-home-from-africa-feeling-very-sick-what-his-doctor-does-is-pure-gold/ using GNOME Web (via a link from Facebook) causes the entire laptop to lock up. The only way to do anything is to attempt (Ctrl-Alt-F1) or a hard reboot.

Computer is a Dell Precision M3800 with NVIDIA Quadro NVS K1100 graphics (Optimus with some Intel GPU -- not sure if actually working -- I didn't confgure anything so its whatever the default config is for it), Core i7 4712HQ processor, 16 GB of RAM. Using default drivers for everything.

Version-Release number of selected component (if applicable):

GNOME Web 3.18 (Webkit 2.10.4)

How reproducible:

Almost every time going to that page

Steps to Reproduce:
1. Open Facebook
2. Find link to that webpage
3. Navigate to it

Actual results:

Computer locks up

Expected results:

Computer doesn't lock up
Additional info:
Comment 1 Michael Catanzaro 2016-03-01 23:57:19 UTC 
*Probably* WebKit #126122, fixed by http://trac.webkit.org/changeset/196803

Please reopen this bug if you still experience the issue once the 2.10.8 update is released (which will probably occur within a week or two).
Note You need to log in before you can comment on or make changes to this bug.