WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
101839
REGRESSION(
r133971
): Causes WebProcess to hang at 100% on www.apple.com (Requested by kling on #webkit).
https://bugs.webkit.org/show_bug.cgi?id=101839
Summary
REGRESSION(r133971): Causes WebProcess to hang at 100% on www.apple.com (Requ...
WebKit Review Bot
Reported
2012-11-10 07:03:26 PST
http://trac.webkit.org/changeset/133971
broke the build: Causes WebProcess to hang at 100% on www.apple.com (Requested by kling 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
Attachments
ROLLOUT of r133971
(19.48 KB, patch)
2012-11-10 07:04 PST
,
WebKit Review Bot
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
WebKit Review Bot
Comment 1
2012-11-10 07:04:06 PST
Created
attachment 173451
[details]
ROLLOUT of
r133971
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.
WebKit Review Bot
Comment 2
2012-11-10 07:13:48 PST
Comment on
attachment 173451
[details]
ROLLOUT of
r133971
Clearing flags on attachment: 173451 Committed
r134157
: <
http://trac.webkit.org/changeset/134157
>
WebKit Review Bot
Comment 3
2012-11-10 07:13:51 PST
All reviewed patches have been landed. Closing bug.
Filip Pizlo
Comment 4
2012-11-10 13:24:12 PST
Wow, sorry for the massive breakage! The bug is that the way I wrote the DFG's optimizations of statements of the form: if (foo) blah !foo I forgot that the empty string evaluates to false in these contexts, and instead wrote the optimization to assume that if I have a string then it's always true. The fix is to change the optimization to exclude strings from the object-isn't-false optimization.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug