New issue
Advanced search Search tips

Issue 665265 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

frame rate drops on Android7.0 webview compared with Android 6.0

Reported by jiad...@gmail.com, Nov 15 2016 
Steps to reproduce the problem:
1. open browser based on webview of Android 7.0, browse www.sina.cn
2. when the page load complete, scroll down and up. check the frame rate using a high speed camera.
3. do the same thing on Android 6.0, compare with the result.

What is the expected behavior?
the frame rate of webview(chromium 51.0.2704.91) is almost the same as the webview on Android 6.0(chromium 44)

What went wrong?
average frame loss about 20% on webview(chromium 51),
compared with 5% on webview(chromium 44)
user may feel a little flicker on when scroll the web page.

we check the systrace comparing the two verion of webview, find that Android Webview IPC-based sync compositing may cause the regression.
please refer the attatchments

Did this work before? N/A 

Chrome version: 51.0.2704.91  Channel: n/a
OS Version: 7.0
Flash Version:

Comment 1 by jiad...@gmail.com, Nov 15 2016 

compared the systraces, we find BrowserMain thread may sync with compositor thread in function RenderWidgetHostViewAndroid::OnVSync and 	BrowserViewRenderer::OnDrawHardware on chromium51, the time duration of these two functions are much shorter on chromium44.

we find a commit https://codereview.chromium.org/1408123005, which add ipc sync message in the situation.if the compositor is handing other message such as those from renderThread, the main thread will be block a little, which may cause flicker on user experience. is there any idea about this?
traceForSina.zip
3.5 MB Download

Comment 2 by rsgav...@chromium.org, Nov 15 2016

Components: Mobile>WebView

Comment 3 by tobiasjs@chromium.org, Nov 16 2016 

You should check a later version of webview. A number of synchronous IPCs have been converted to async in the interim, but the change you mention was key to the multiprocess efforts that happened in N.

Comment 4 by torne@chromium.org, Nov 16 2016 

Also, you should compare either different webview versions, or different OS versions, but not both at the same time.

Comment 5 by gsennton@chromium.org, Nov 21 2016

Labels: Needs-Feedback
I believe the most recently released version of WebView released by now is 54, so it might be good to check against that?
Project Member

Comment 6 by sheriffbot@chromium.org, Dec 21 2016

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "jiadzhu@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment