Issue metadata
Sign in to add a comment
|
WebView occasionally shows nothing when load page
Reported by
lfimmort...@gmail.com,
May 26 2016
|
||||||||||||||||||||||||
Issue descriptionDevice name: Xiaomi Mi4, Xiaomi Mi Note, Moto X Style Android version: 5.1.1, 6.0 WebView version (from system settings -> Apps -> Android System WebView): 50.0.2661.86 (Current version in Google Play) WebView version 50.0.2661.35 and 46.0.2490.76 do not reproduce this problem. Application: Xiaomi App Market, our Demo(https://github.com/lfimmortal/WebView-Blank-Page-Demo/) Application version: URLs (if applicable): Steps to reproduce: (1) Install our demo application, demo web pages are attached in it (2) Click "Load" button to load page (3) Repeat several times Expected result: Pages display normally Actual result: With a probability about 1/10, WebView shows nothing. In this state, utime and stime of thread Chrome_InProcRendererThread and Chrome_InProcGpuThread grow continuous. Then lock and unlock the device, the blank white page will turn to display normally.
,
Jun 1 2016
Updated the demo. Now activity will be finished after launch a now one. With this change, I can still reproduce the problem on my devices. In previous version, activity was not finished because we thought this may increase the chance of problem. However, even if that is true, the effect is not significant.
,
Jun 1 2016
Doesn't really matter since we can't reproduce the issue either way. Can you take a chrome trace of just "Click Load, and webview shows nothing". Take a new trace each time before clicking load, and include one where the webview is blank. https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-from-Chrome-on-Android-with-DevTools- Include all default categories (on the left) and cc.debug on the right.
,
Jun 2 2016
Trace: https://github.com/lfimmortal/WebView-Blank-Page-Demo/tree/master/trace 4s to 12s in the trace shows the abnormal state. After that I locked and onlocked the phone, and then the page appeared normally. Trace of a normal loading is attached for reference.
,
Jun 3 2016
I see 0MB memory policy on trace_issue.json. That means somehow, either the renderer never gets a non-zero memory policy, or browser never assigns a non-zero memory policy to renderer. Maybe this is same as crbug.com/613781 .
,
Jun 3 2016
,
Jun 3 2016
This was m50, which was before we made set memory policy IPC asynchronous.
,
Jun 3 2016
this is the memory policy livelock thing I've seen before, I thought I fixed that already though, let me dig up the fix.. what webview version are you using here exactly?
,
Jun 3 2016
https://bugs.chromium.org/p/chromium/issues/detail?id=611729 Fix was merged to m51. It was too late for m50 iirc |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by boliu@chromium.org
, May 31 2016