New issue
Advanced search Search tips

Issue 921586 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 921239
Owner:
Closed: Jan 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.2%-39% regression in v8.browsing_desktop at 621730:621894

Project Member Reported by petermarshall@chromium.org, Jan 14

Issue description

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

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


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

Win 7 Nvidia GPU Perf
linux-perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None

oortonline_tbmv2 - Benchmark documentation link:
  None
Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Unconfirmed)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16cf8488540000

[heap] Remove bailout marking worklist. by ulan@chromium.org
https://chromium.googlesource.com/v8/v8/+/68a8bdd82988d6ae1d9769748d58fc8b266e8c9a
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size: 7.889e+07 → 9.837e+07 (+1.948e+07)

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

Benchmark documentation link:
  None
Mergedinto: 921239
Status: Duplicate (was: Assigned)

Sign in to add a comment