New issue
Advanced search Search tips

Issue 821430 link

Starred by 1 user
Status: Duplicate
Merged: issue 821585
Owner:
zmo@chromium.org
Closed: Mar 2018
Cc:
geoffl...@chromium.org
hjd@google.com
zmo@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23587.3% regression in memory.desktop at 541437:541557

Project Member Reported by hjd@google.com, Mar 13 2018 
Jumped from ~24kb to ~6mb -> got to be some kind of accounting bug or a flag flip.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 13 2018 

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

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


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

chromium-rel-win7-gpu-intel
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 13 2018

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

Disable D3D11 on Win7 if basic GPUInfo collection fails. by zmo@chromium.org
https://chromium.googlesource.com/chromium/src/+/f0bbf84ef7520774f0c26c819b01014c651ae5ac

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

Comment 4 by zmo@chromium.org, Mar 13 2018

Mergedinto: 821585
Status: Duplicate (was: Assigned)
This is because we switch from SwiftShader to D3D.

This GPU perf bot should not have run with SwiftShader in the first place.
►

Sign in to add a comment