Bug 139632

Summary: REGRESSION(r177238): Introduced memory corruption (Requested by ap on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, dino, simon.fraser
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 136410, 139596    
Attachments:
Description Flags
ROLLOUT of r177238 none

WebKit Commit Bot
Reported 2014-12-14 18:45:58 PST
http://trac.webkit.org/changeset/177238 broke the build: Introduced memory corruption (Requested by ap 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.
Attachments
ROLLOUT of r177238 (12.21 KB, patch)
2014-12-14 18:46 PST, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2014-12-14 18:46:32 PST
Created attachment 243277 [details] ROLLOUT of r177238 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 Commit Bot
Comment 2 2014-12-14 18:49:40 PST
Comment on attachment 243277 [details] ROLLOUT of r177238 Clearing flags on attachment: 243277 Committed r177269: <http://trac.webkit.org/changeset/177269>
WebKit Commit Bot
Comment 3 2014-12-14 18:49:44 PST
All reviewed patches have been landed. Closing bug.
Simon Fraser (smfr)
Comment 4 2014-12-14 21:07:18 PST
Where is a link to the relevant test failures?
Alexey Proskuryakov
Comment 6 2014-12-14 21:16:13 PST
I posted the information into the original re-opened bug. There was indeed no link, because the crash logs are not as helpful without GuardMalloc. But yes, you found the right one from bots.
Note You need to log in before you can comment on or make changes to this bug.