New issue
Advanced search Search tips

Issue 856830 link

Starred by 1 user
Status: Duplicate
Owner:
jdarpinian@chromium.org
Closed: Jun 2018
Cc:
m...@chromium.org
jdarpinian@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2%-51200% regression in system_health.memory_mobile at 568483:568659

Project Member Reported by m...@chromium.org, Jun 26 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 26 2018 

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

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


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

android-nexus5
android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 27 2018

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

GPU: Don't flush when destroying transfer buffers. by jdarpinian@chromium.org
https://chromium.googlesource.com/chromium/src/+/d1b4ae2892b05cf622b3f649cb38b995ed2d1733
2048 → 1.051e+06 (+1.049e+06)

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

Comment 4 by jdarpinian@chromium.org, Jun 30 2018

Mergedinto: 855402
Status: Duplicate (was: Assigned)
►

Sign in to add a comment