New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 874955 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 874437
Owner:
Last visit > 30 days ago
Closed: Aug 21
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-163% regression in v8.browsing_mobile at 582169:583278

Project Member Reported by hpayer@google.com, Aug 16

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1184ac56640000

[heap] Use std::atomic for page flags. by hpayer@chromium.org
https://chromium.googlesource.com/v8/v8/+/7f3f7e8a9547ece1a7f80ce902bc23632e902b0b
3.35 → 7.743 (+4.393)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 874437
Status: Duplicate (was: Assigned)
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12dbd3ec640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.

Sign in to add a comment