New issue
Advanced search Search tips

Issue 917246 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

10% regression in system_health.memory_desktop at 616409:616468

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=917246

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


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

mac-10_13_laptop_high_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/16e281ce140000

[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:gpu:effective_size: 6.053e+07 → 6.654e+07 (+6.008e+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