New issue
Advanced search Search tips

Issue 893825 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 893790
Owner:
Closed: Oct 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.4%-247.6% regression in blink_perf.canvas at 595918:596000

Project Member Reported by m...@chromium.org, Oct 9

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

blink_perf.canvas - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: aaronhk@google.com
Owner: aaronhk@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11ff2a22e40000

Update canvas memory usage calculation by aaronhk@google.com
https://chromium.googlesource.com/chromium/src/+/4e1d4919de4b25e7a53edf095f3fdf2ddead0910
toBlob_duration: 1.143e+04 → 3.547e+04 (+2.403e+04)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: fs...@chromium.org
Mergedinto: 893790
Status: Duplicate (was: Assigned)

Sign in to add a comment