New issue
Advanced search Search tips

Issue 856841 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.3% regression in system_health.memory_mobile at 568483:568607

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=856841

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


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

android-nexus5
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/11cee75b240000

GPU: Don't flush when destroying transfer buffers. by jdarpinian@chromium.org
https://chromium.googlesource.com/chromium/src/+/d1b4ae2892b05cf622b3f649cb38b995ed2d1733
5.219e+07 → 5.344e+07 (+1.254e+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