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

Issue 832122 link

Starred by 2 users
Status: WontFix
Owner:
jarin@chromium.org
Closed: Apr 2018
Cc:
jarin@chromium.org
█ eakuefner@chromium.org
toyoshim@chromium.org
mstarzinger@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5% regression in octane at 549610:549693

Project Member Reported by 42576172...@developer.gserviceaccount.com, Apr 12 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 14 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/128a2372c40000

[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 4 by jarin@chromium.org, Apr 23 2018

Status: WontFix (was: Assigned)
This re-enables protection removed by https://chromium.googlesource.com/v8/v8/+/1ef6c4374ebf9448c71107a66382a6a0b1a31c68.

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

Cc: toyoshim@chromium.org
 Issue 833265  has been merged into this issue.

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

 Issue 833294  has been merged into this issue.
►

Sign in to add a comment