Bug 151417

Summary: REGRESSION(r192436): Caused a hang in the inspector and a crash @ google.com. (Requested by saamyjoon on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: ggaren, keith_miller, mark.lam, msaboff, sbarati
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 151026, 151369    
Attachments:
Description Flags
ROLLOUT of r192436 none

Description WebKit Commit Bot 2015-11-18 15:51:45 PST
http://trac.webkit.org/changeset/192436 broke the build:
Caused a hang in the inspector and a crash @ google.com. (Requested by saamyjoon on #webkit).

This is an automatic bug report generated by webkitbot. If this bug
report was created because of a flaky test, please file a bug for the flaky
test (if we don't already have one on file) and dup this bug against that bug
so that we can track how often these flaky tests fail.
Comment 1 WebKit Commit Bot 2015-11-18 15:52:18 PST
Created attachment 265795 [details]
ROLLOUT of r192436

Any committer can land this patch automatically by marking it commit-queue+.  The commit-queue will build and test the patch before landing to ensure that the rollout will be successful.  This process takes approximately 15 minutes.

If you would like to land the rollout faster, you can use the following command:

  webkit-patch land-attachment ATTACHMENT_ID

where ATTACHMENT_ID is the ID of this attachment.
Comment 2 Saam Barati 2015-11-18 16:00:32 PST
*** Bug 151419 has been marked as a duplicate of this bug. ***
Comment 3 WebKit Commit Bot 2015-11-18 16:03:31 PST
Comment on attachment 265795 [details]
ROLLOUT of r192436

Clearing flags on attachment: 265795

Committed r192597: <http://trac.webkit.org/changeset/192597>
Comment 4 WebKit Commit Bot 2015-11-18 16:03:33 PST
All reviewed patches have been landed.  Closing bug.
Comment 5 Csaba Osztrogon√°c 2015-11-19 03:11:33 PST
*** Bug 151416 has been marked as a duplicate of this bug. ***