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

Issue 913498 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ chromium...@skia-public.iam.gserviceaccount.com
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

165.2% regression in system_health.memory_desktop at 603484:603845

Project Member Reported by npm@chromium.org, Dec 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

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

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


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

Win 7 Nvidia GPU Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 12

Cc: chromium...@skia-public.iam.gserviceaccount.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14d7feca140000

Roll src/third_party/skia c09dc8ac723f..71652e2a09b7 (3 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/bb9b07495bd7d17f632c21cdfe5018fe7bc9f813
memory:chrome:all_processes:reported_by_chrome:skia:effective_size: 4.553e+05 → 1.255e+06 (+7.995e+05)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Comment 4 by benhenry@google.com, Jan 11

Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner
►

Sign in to add a comment