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

Issue 883817 link

Starred by 1 user
Status: WontFix
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Sep 14
Cc:
█ kbr@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression

Blocking:
issue 882317



Sign in to add a comment

41.3% regression in rendering.desktop at 590069:590187

Project Member Reported by npm@chromium.org, Sep 13 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 13 

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

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


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

mac-10_12_laptop_low_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 14

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

Restrict FlushForDriverCrashWorkaround to non-WebGL contexts. by kbr@chromium.org
https://chromium.googlesource.com/chromium/src/+/4dc2e915fde1b77566d7ccd721e2b990a7f976f3
57.82 → 36.07 (-21.75)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by kbr@chromium.org, Sep 14

Blocking: 882317
Components: Blink>WebGL
Labels: OS-Mac
Status: WontFix (was: Assigned)
If the only regression with that change is on the smoothness.tough_webgl_cases/dynamic_cube_map story on a low-end Mac, this is a definite WontFix.
►

Sign in to add a comment