New issue
Advanced search Search tips

Issue 911471 link

Starred by 1 user
Status: WontFix
Owner:
verwa...@chromium.org
Closed: Dec 5
Cc:
verwa...@chromium.org
toyoshim@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-3.3% regression in system_health.memory_mobile at 611366:611529

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

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

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

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


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

Android Nexus5X WebView Perf
android-nexus5x-perf

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

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

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

Cc: verwa...@chromium.org
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17cedf42140000

[zone] Revert to previous zone allocation strategies due to severe memory regressions. by verwaest@chromium.org
https://chromium.googlesource.com/v8/v8/+/de20e6d3a855d7dc4a991dd192052c30b6ea996e
memory:webview:all_processes:reported_by_chrome:malloc:effective_size: 3.593e+07 → 3.684e+07 (+9.169e+05)

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

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

Comment 4 by verwa...@chromium.org, Dec 5

Status: WontFix (was: Assigned)
It's a revert due to memory regressions in other places.
►

Sign in to add a comment