New issue
Advanced search Search tips

Issue 901367 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 888558
Owner:
Closed: Nov 2
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% regression in memory:webview:all_processes:reported_by_chrome:malloc:effective_size at 603899:603943

Project Member Reported by 42576172...@developer.gserviceaccount.com, Nov 2

Issue description

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

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


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

Android Nexus5X WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: oysteine@chromium.org
Owner: oysteine@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13ad365ee40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
memory:webview:all_processes:reported_by_chrome:malloc:effective_size: 2.995e+07 → 3.03e+07 (+3.545e+05)

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

Benchmark documentation link:
  None
Mergedinto: 888558
Status: Duplicate (was: Assigned)

Sign in to add a comment