Bug 86251

Summary: REGRESSION(r116498): Causes crashes in major sites and security issues (Requested by schenney on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Severity: Normal CC: darin, eric, inferno, pdr, schenney, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 83405    
Description Flags
ROLLOUT of r116498 none

Description WebKit Review Bot 2012-05-11 14:01:14 PDT
http://trac.webkit.org/changeset/116498 broke the build:
Causes crashes in major sites and security issues (Requested by schenney on #webkit).

This is an automatic bug report generated by the sheriff-bot. 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 case pain.

"Only you can prevent forest fires." -- Smokey the Bear
Comment 1 WebKit Review Bot 2012-05-11 14:01:55 PDT
Created attachment 141491 [details]
ROLLOUT of r116498

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 WebKit Review Bot 2012-05-11 14:11:20 PDT
Comment on attachment 141491 [details]
ROLLOUT of r116498

Clearing flags on attachment: 141491

Committed r116801: <http://trac.webkit.org/changeset/116801>
Comment 3 WebKit Review Bot 2012-05-11 14:11:25 PDT
All reviewed patches have been landed.  Closing bug.
Comment 4 Philip Rogers 2012-05-11 14:24:27 PDT
This was rolled out due to being the #1 cause of crashes in Chrome.

It caused at least two distinct bugs:
1) https://bugs.webkit.org/show_bug.cgi?id=86166
2) http://code.google.com/p/chromium/issues/detail?id=127418