New issue
Advanced search Search tips

Issue 896331 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 17
Cc:
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.3%-80% regression in memory:chrome:all_processes:reported_by_chrome:cc:effective_size at 600027:600187

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 17 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 17 

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

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


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

linux-perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 17 

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

Comment 4 by sullivan@chromium.org, Oct 17

Status: WontFix (was: Untriaged)
Just realized the ref build moves too. Bisect can't repro, likely not a real issue.
►

Sign in to add a comment