New issue
Advanced search Search tips

Issue 897128 link

Starred by 1 user
Status: Duplicate
Owner:
herb@google.com
Closed: Oct 31
Cc:
hjd@google.com
herb@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4% regression in memory.top_10_mobile at 600274:600303

Project Member Reported by hjd@google.com, Oct 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 19 

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

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


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

Android Nexus6 WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 19

Cc: herb@google.com
Owner: herb@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1477101ae40000

Reland "Have GrAtlasManager use legacy behavior" by herb@google.com
https://skia.googlesource.com/skia/+/bbf5fb5be451174f8a3671927a263069e1a02853
memory:webview:all_processes:reported_by_chrome:malloc:effective_size: 2.018e+07 → 2.048e+07 (+2.956e+05)

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

Benchmark documentation link:
  None

Comment 4 by herb@google.com, Oct 31

Mergedinto: 896363
Status: Duplicate (was: Assigned)
►

Sign in to add a comment