New issue
Advanced search Search tips

Issue 917236 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 917247
Owner:
Closed: Dec 21
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1% regression in system_health.memory_desktop at 616350:616447

Project Member Reported by kouhei@google.com, Dec 21

Issue description

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

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


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

mac-10_12_laptop_low_end-perf

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

[PE] Avoid cache conflict when painting LocalFrameView outside of lifecycle by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/81fc6554b2da741da30913dee5008cc83b20091d
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 5.806e+07 → 5.927e+07 (+1.209e+06)

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

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

Sign in to add a comment