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

Issue 836483 link

Starred by 2 users
Status: Assigned
Owner:
jkummerow@chromium.org
Cc:
jkummerow@chromium.org
leszeks@chromium.org
█ briander...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11.6% regression in blink_perf.bindings at 550911:550914

Project Member Reported by briander...@chromium.org, Apr 24 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win7-dual
Project Member

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

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

[ubsan] Change Address typedef to uintptr_t by jkummerow@chromium.org
https://chromium.googlesource.com/v8/v8/+/2459046c1dd5bc2d07e5fe776bf40423f3722deb

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

Sign in to add a comment