New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 798349 link

Starred by 1 user
Status: WontFix
Owner:
xing...@intel.com
Closed: Mar 2018
Cc:
danakj@chromium.org
xing...@intel.com
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1%-21.3% regression in system_health.memory_desktop at 525717:525826

Project Member Reported by alexclarke@chromium.org, Jan 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 2 2018 

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

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


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

chromium-rel-mac12
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 2 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14932603040000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 3 2018 

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

Comment 8 by sullivan@chromium.org, Jan 25 2018 

Re-kicking bisects on a wider range.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 26 2018

Cc: danakj@chromium.org xing...@intel.com
Owner: xing...@intel.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint.chromeperf.appspot.com/job/149fd75c840000

[viz] Implement local resource in GLRenderer
By xing.xu@intel.com · Fri Dec 22 02:20:01 2017
chromium @ 9cc56b283e51de94cc373a77214da2bb646efcbd

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

Comment 10 by 42576172...@developer.gserviceaccount.com, Jan 26 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint.chromeperf.appspot.com/job/14c07bc2840000

[viz] Implement local resource in GLRenderer
By xing.xu@intel.com · Fri Dec 22 02:20:01 2017
chromium @ 9cc56b283e51de94cc373a77214da2bb646efcbd

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

Comment 11 by xing...@intel.com, Jan 26 2018 

Maybe this duplicate 
https://bugs.chromium.org/p/chromium/issues/detail?id=797390?
Memory moved from gpu to cc.

Comment 12 by xing...@intel.com, Mar 27 2018 

Hi,as we have reached a consensus, this isn’t memory regression, but memory was calculated from cc tag to gpu tag. And the new memory tag viz will be used instead(crbug.com/800238). So how about close this one and track it in the viz memory dump issue?

Comment 13 by xing...@intel.com, Mar 28 2018

Status: WontFix (was: Assigned)
Mark this as WontFix, for further action, please refer to: crbug.com/800238.
►

Sign in to add a comment