New issue
Advanced search Search tips

Issue 856829 link

Starred by 1 user
Status: WontFix
Owner:
boliu@chromium.org
Closed: Jun 2018
Cc:
m...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.4% regression in smoothness.tough_path_rendering_cases at 568139:568365

Project Member Reported by m...@chromium.org, Jun 26 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 26 2018 

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

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


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 27 2018

Cc: jamwalla@chromium.org
Owner: jamwalla@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/128806f0a40000

AW: Don't draw if PrepareTiles is needed and no damage by jamwalla@chromium.org
https://chromium.googlesource.com/chromium/src/+/fbb0e336a2d6fe1237aecbb9cdfaa59e252857fa
147.1 → 171.1 (+23.96)

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

Comment 4 by jamwalla@chromium.org, Jun 27 2018

Owner: boliu@chromium.org
:(

Comment 5 by jamwalla@chromium.org, Jun 27 2018

Cc: -jamwalla@chromium.org

Comment 6 by boliu@chromium.org, Jun 29 2018

Components: Mobile>WebView
Labels: OS-Android
Status: WontFix (was: Assigned)
that's regression by roughly one frame. I think that's expected in some cases, if frames aren't already spinning, and might need an additional frame to request real invalidate to get this to work.

seems like an acceptable trade off to me for significant power savings
►

Sign in to add a comment