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

Issue 604006 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1MB regression in sizes at 386991:386999

Project Member Reported by rsch...@chromium.org, Apr 15 2016

Issue description

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=604006

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-Ny6ogoM


Bot(s) for this bug's original alert(s):

Google Chrome Linux x64
Owner: rsch...@chromium.org
In my local release build, the binary size of Blink is identical before and after my change (as I'd expect). I also don't see it in the range shown in the dashboard.
Cc: nyerramilli@chromium.org
Labels: TE-Triaged
gentle ping..
Cc: ashej...@chromium.org
@rschoen: Friendly Ping!
Status: WontFix (was: Assigned)
Bulk-closing sizes regressions as we were looking at the wrong metric, should have been tracking ChromiumChrome/Google Chrome Linux x64/sizes/chrome-stripped/stripped

Sign in to add a comment