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

Issue 852973 link

Starred by 1 user
Status: WontFix
Owner:
mlippautz@chromium.org
Closed: Aug 8
Cc:
mlippautz@chromium.org
█ briander...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

164.3% regression in memory.long_running_idle_gmail_tbmv2 at 564821:564870

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

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

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

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


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

android-nexus5X
Project Member

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

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

[oilpan] Move stats from ThreadHeapStats to ThreadHeapStatsCollector by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/a28edd7823a5e5d6c3f524c9e5b6202b0ff655f0
52.2 → 140.8 (+88.58)

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

Comment 4 by mlippautz@chromium.org, Aug 8

Status: WontFix (was: Assigned)
v8-gc-total max is not interesting; we only care about the sum for this one.
►

Sign in to add a comment