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

Issue 875816 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 26
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

30.9%-66.1% regression in v8.browsing_mobile at 582919:583026

Project Member Reported by petermarshall@chromium.org, Aug 20

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16aa9281640000
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12bd52ee640000
Cc: hpayer@chromium.org
Owner: hpayer@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/159811b1640000

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

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Fixed (was: Assigned)

Sign in to add a comment