New issue
Advanced search Search tips

Issue 916454 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.2%-34.7% regression in v8.browsing_desktop at 617015:617064

Project Member Reported by mlippautz@chromium.org, Dec 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=916454

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


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

Win 7 Perf
linux-perf
mac-10_12_laptop_low_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None
Cc: peria@chromium.org
Owner: peria@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11dd03f1140000

binding: Drop a runtime enabled flag for V8ContextSnapshot by peria@chromium.org
https://chromium.googlesource.com/chromium/src/+/ff19f4443204410b3be71c476d23c716db18c800
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size: 2.031e+07 → 2.661e+07 (+6.3e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Status: Fixed (was: Assigned)
r617061 seems to have fixed this issue.

Sign in to add a comment