New issue
Advanced search Search tips

Issue 924348 link

Starred by 0 users
Status: WontFix
Owner:
thomasanderson@chromium.org
Closed: Today
Cc:
tapted@chromium.org
thakis@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

0.8% regression in sizes at 624189:624207

Project Member Reported by tapted@google.com, Today (6 hours ago) 
Just linking the exception on the perf graph to a bug..

I expect this is r624193 "Switch Mac to in-tree libc++ builds"
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Today (6 hours ago) 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a5d141307ee0c12e0eeb337c6223f84a84adf7497a27689ccb4e78d01cbb6dc2


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

Google Chrome Mac

Comment 2 by tapted@chromium.org, Today (6 hours ago) 

Note the graphs report a delta of 202138000 -> 203850000, or 1,671 KiB - much more than the 512KiB stated in the CL description.

Comment 3 by thomasanderson@chromium.org, Today (6 hours ago)

Labels: OS-Mac
Status: WontFix (was: Assigned)
That is a bit more than I expected, but seems reasonable now given that the system libc++.1.dylib is 1441 Kib, so 1671 KiB isn't too far off.  We also use a different build config than the system libc++ (_LIBCPP_ABI_UNSTABLE) which increases binary size a bit further to reap some performance improvements.
►

Sign in to add a comment