New issue
Advanced search Search tips

Issue 825581 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 25
Cc:
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6%-13% regression in system_health.memory_desktop at 544564:544985

Project Member Reported by sullivan@chromium.org, Mar 25 2018 
These all drop down and then go up again. The drop corresponds to r543955, "Automate calls to GrContext::resetContext" and the bump up corresponds to its revert.  Cc-in author junov but will wait for bisect.
Project Member

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

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

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

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

Revert "Automate calls to GrContext::resetContext" by junov@chromium.org
https://chromium.googlesource.com/chromium/src/+/60f840e7e212c79d76e5e7fa32667214e050e20b

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

Comment 4 by junov@chromium.org, Jul 25

Cc: -junov@chromium.org

Comment 5 by junov@chromium.org, Jul 25

Owner: ----
Status: Available (was: Assigned)

Comment 6 by sullivan@chromium.org, Jul 25

Status: WontFix (was: Available)
WontFix-ing this since the root cause is a revert.
►

Sign in to add a comment