New issue
Advanced search Search tips

Issue 892071 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5% regression in speedometer2 at 592336:592418

Project Member Reported by tebbi@chromium.org, Oct 4

Issue description

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

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


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

Win 7 Perf

speedometer2 - Benchmark documentation link:
  None
Cc: jarin@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1352bc1ce40000

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
Elm-TodoMVC: 435.5 → 459.9 (+24.47)

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

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

Sign in to add a comment