New issue
Advanced search Search tips

Issue 897112 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 897115
Owner:
Closed: Oct 23
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

59.6% regression in system_health.memory_desktop at 600092:600256

Project Member Reported by hjd@google.com, Oct 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=897112

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


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

Win 7 Perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: andrescj@chromium.org
Owner: andrescj@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17ca6a4ee40000

Disallow libjpeg_turbo downscaling of images with non-whole MCUs. by andrescj@chromium.org
https://chromium.googlesource.com/chromium/src/+/8b9172a61f4e507b2eef30b2af438d2c19c0992d
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 1.055e+08 → 1.692e+08 (+6.365e+07)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 897115
Status: Duplicate (was: Assigned)

Sign in to add a comment