New issue
Advanced search Search tips

Issue 638017 link

Starred by 1 user
Status: WontFix
Owner:
dgozman@chromium.org
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

0.3% regression in sizes at 411882:411882

Project Member Reported by benjhayden@chromium.org, Aug 15 2016 
See the link to graphs below.

Comment 1 by benjhayden@chromium.org, Aug 15 2016 

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

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


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

mac

Comment 2 by rsch...@chromium.org, Sep 23 2016

Owner: dgozman@chromium.org
This is fairly old at this point, but in these cases we know exactly which CL is responsible (the range is only 1 CL long).

dgozman, looks like 16523d99c644c8513ad586eaca935fa2bea877b1 significantly increased binary size. Was that expected?

Comment 3 by dgozman@chromium.org, Sep 24 2016

Status: WontFix (was: Assigned)
That's possible. However, it should have changed back after https://chromium.googlesource.com/chromium/src.git/+/0ca1f564f9660554511191fbd38bec101ca6f08d, and I see a positive change at that revision (although it's smaller).
►

Sign in to add a comment