Bug 139632 - REGRESSION(r177238): Introduced memory corruption (Requested by ap on #webkit).
Summary: REGRESSION(r177238): Introduced memory corruption (Requested by ap on #webkit).
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: WebKit Commit Bot
Depends on:
Blocks: 136410 139596
  Show dependency treegraph
Reported: 2014-12-14 18:45 PST by WebKit Commit Bot
Modified: 2014-12-14 21:16 PST (History)
3 users (show)

See Also:

ROLLOUT of r177238 (12.21 KB, patch)
2014-12-14 18:46 PST, WebKit Commit Bot
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Commit Bot 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.
Comment 1 WebKit Commit Bot 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.
Comment 2 WebKit Commit Bot 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>
Comment 3 WebKit Commit Bot 2014-12-14 18:49:44 PST
All reviewed patches have been landed.  Closing bug.
Comment 4 Simon Fraser (smfr) 2014-12-14 21:07:18 PST
Where is a link to the relevant test failures?
Comment 6 Alexey Proskuryakov 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.