New issue
Advanced search Search tips

Issue 833294 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 832122
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4%-5.5% regression in octane at 549492:549672

Project Member Reported by toyoshim@chromium.org, Apr 16 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 16 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=833294

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


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

chromium-rel-mac11-air
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 16 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/11c24bcac40000
run another bisect with wider range specified
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 16 2018

Cc: jarin@chromium.org mstarzinger@chromium.org
Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c738fac40000

[turbofan] Re-enable stack pointer poisoning. by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/963062fb73a9c2f59e4a6463524a81d3e86e2444

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

Comment 7 by jarin@chromium.org, Apr 23 2018

Mergedinto: 832122
Status: Duplicate (was: Assigned)

Sign in to add a comment