New issue
Advanced search Search tips

Issue 874896 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5% regression in rendering.mobile at 582102:582122

Project Member Reported by tdres...@chromium.org, Aug 16

Issue description

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

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


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

Android Nexus6 WebView Perf
Cc: mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1485d166640000

Oilpan: Enable incremental marking per default by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/f789a9453217467376d32c4d20b67501e48f3129
11.09 → 11.37 (+0.2791)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
WontFix as it is a single regression on a single device/benchmark. I also cannot find the renderer in the trace.

Sign in to add a comment