New issue
Advanced search Search tips

Issue 774280 link

Starred by 1 user
Status: Duplicate
Merged: issue 775502
Owner:
jkummerow@chromium.org
Closed: Oct 2017
Cc:
huangs@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16KiB regression in resource_sizes (MonochromePublic.apk) at 508230:508230

Project Member Reported by huangs@google.com, Oct 12 2017 
Caused by “[bigint] Support BigInts in <<,>>,>>>,&,|,^ binary ops”

Commit: 1560988249c97c5cc1763aa364a0423f9e318c13 (v8)
https://chromium-review.googlesource.com/c/v8/v8/+/699424

Link to size graph: https://chromeperf.appspot.com/report?sid=a097e74b1aa288511afb4cb616efe0f95ba4d347ad61d5e835072f23450938ba&num_points=10&rev=480214

Debugging size regressions is documented at: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase

Based on the graph: 15KiB of native code.

It looks like this increase was probably unexpected or might be avoidable.
Please have a look and either:

Close as “Won't Fix” with a short justification, or
Land a revert / fix-up.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 12 2017 

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

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


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

Android Builder

Comment 2 by jkummerow@chromium.org, Oct 19 2017

Mergedinto: 775502
Status: Duplicate (was: Assigned)
Implementing new features unfortunately costs binary size.
►

Sign in to add a comment