New issue
Advanced search Search tips

Issue 825107 link

Starred by 3 users
Status: WontFix
Owner:
danakj@chromium.org
Closed: Mar 2018
Cc:
danakj@chromium.org
chiniforooshan@chromium.org
kylec...@chromium.org
sullivan@chromium.org
sky@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

86.9% regression in system_health.memory_mobile at 544345:544418

Project Member Reported by chiniforooshan@chromium.org, Mar 23 2018 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5X
Project Member

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16d59439440000

Comment 5 by chiniforooshan@chromium.org, Mar 23 2018 

Bisecting a wider range.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Mar 23 2018

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

Allocate shared memory/textures directly for UIResources. by danakj@chromium.org
https://chromium.googlesource.com/chromium/src/+/f77a89225113b8f47f36670265fb9130502170ca

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

Comment 7 by danakj@chromium.org, Mar 23 2018

Status: WontFix (was: Assigned)
This moved allocation reporting from ResourceProvider to LayerTreeHostImpl

Comment 8 by chiniforooshan@chromium.org, Mar 26 2018 

 Issue 824385  has been merged into this issue.

Comment 9 by chiniforooshan@chromium.org, Mar 26 2018 

 Issue 824201  has been merged into this issue.

Comment 10 by chiniforooshan@chromium.org, Mar 26 2018 

So, should we see a corresponding ~1M memory usage drop in another graph?

Comment 12 by sullivan@chromium.org, Mar 28 2018

Cc: sullivan@chromium.org
 Issue 825583  has been merged into this issue.

Comment 13 by danakj@chromium.org, Mar 29 2018 

Issue 825624 has been merged into this issue.

Comment 14 by kylec...@chromium.org, Apr 13 2018 

Issue 824767 has been merged into this issue.
►

Sign in to add a comment