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

Issue 825606 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5% regression in system_health.memory_desktop at 545025:545111

Project Member Reported by sullivan@chromium.org, Mar 25 2018

Issue description

See the link to graphs below.
 
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=825606

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


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

chromium-rel-mac11-air
Project Member

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

Cc: primiano@chromium.org erikc...@chromium.org ajwong@chromium.org
Owner: erikc...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11d1f5a3440000

Correct macOS private memory footprint calculations. by erikchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/7c1d03f55ec7a248aece22abfdef25e100bcf4f4

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
WAI - this was an accounting change.

Sign in to add a comment