New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 627873 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
cwp

Blocking:
issue 382705



Sign in to add a comment

Runtime memory leak detector should record Chrome binary build ID in leak reports

Project Member Reported by sque@chromium.org, Jul 13 2016

Issue description

The build ID is necessary for symbolization.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 15 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/84bb999bd0ed887c26f04f58715fda5b03271f90

commit 84bb999bd0ed887c26f04f58715fda5b03271f90
Author: sque <sque@chromium.org>
Date: Fri Jul 15 22:37:39 2016

Add build ID field to MemoryLeakReportProto

BUG= chromium:627873 
TEST=build successfully

Review-Url: https://codereview.chromium.org/2158583002
Cr-Commit-Position: refs/heads/master@{#405883}

[modify] https://crrev.com/84bb999bd0ed887c26f04f58715fda5b03271f90/components/metrics/proto/memory_leak_report.proto

Comment 3 by sque@chromium.org, Jul 25 2016

Status: Fixed (was: Assigned)
Labels: VerifyIn-54
Status: Verified (was: Fixed)
bulk verified

Sign in to add a comment