New issue
Advanced search Search tips

Issue 897123 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 31
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.5% regression in memory.top_10_mobile at 600274:600303

Project Member Reported by hjd@google.com, Oct 19

Issue description

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

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


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

Android Nexus6 WebView Perf

memory.top_10_mobile - Benchmark documentation link:
  None
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/144d1132e40000

Reland "Have GrAtlasManager use legacy behavior" by herb@google.com
https://skia.googlesource.com/skia/+/bbf5fb5be451174f8a3671927a263069e1a02853
memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size: 2.723e+07 → 2.767e+07 (+4.391e+05)

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

Benchmark documentation link:
  None
Cc: bsalo...@google.com
 Issue 897124  has been merged into this issue.
Mergedinto: 896363
Status: Duplicate (was: Assigned)

Sign in to add a comment