Bug 53256

Summary: REGRESSION(r76825): "caused crashes on GTK and chromium" (Requested by rniwa on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, darin, eric, rniwa, senorblanco
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
ROLLOUT of r76825 none

WebKit Review Bot
Reported 2011-01-27 13:50:31 PST
http://trac.webkit.org/changeset/76825 broke the build: "caused crashes on GTK and chromium" (Requested by rniwa 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 r76825 (8.35 KB, patch)
2011-01-27 13:50 PST, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2011-01-27 13:50:52 PST
Created attachment 80362 [details] ROLLOUT of r76825 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 --ignore-builders where ATTACHMENT_ID is the ID of this attachment.
Ryosuke Niwa
Comment 2 2011-01-27 14:02:15 PST
Comment on attachment 80362 [details] ROLLOUT of r76825 Clearing flags on attachment: 80362 Committed r76836: <http://trac.webkit.org/changeset/76836>
Ryosuke Niwa
Comment 3 2011-01-27 14:02:18 PST
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 4 2011-01-27 14:48:04 PST
http://trac.webkit.org/changeset/76836 might have broken GTK Linux 64-bit Debug
Note You need to log in before you can comment on or make changes to this bug.