Android webview crashes when only the software renderer is present
Reported by
wolf...@wiedmeyer.de,
Mar 26 2016
|
||
Issue descriptionDevice name: Samsung Galaxy S3 (GT-I9300) running Replicant Application version: 51.0.2691.1 OS: Android 6.0.1 Steps to reproduce: Start Android Browser on a device that only provides a software renderer. Expected result: Does not crash. Actual result: The Webview crashes immediately. The crashes first appeared with v45. This commit was introduced to force auxiliary bitmap for the emulator: https://chromium.googlesource.com/chromium/src.git/+/892c566fd38456475e8e58501f4f6c7373d82a3c Forcing auxiliary bitmap not only for the emulator, but at any time by setting the variables always to true, does not help and results in the same crash. Logcat for v51.0.2691.1 is attached. I also attached the log for version 49.0.2623.91 if it's helpful, but it looks basically the same. Version 43.0.2357.134 was the last one that didn't crash. I know that devices without OpenGL ES 2.0 support are not officially supported anymore, but this also affects the emulator without host gpu in the same way. Related issues with the emulator and the software renderer: https://code.google.com/p/android/issues/detail?id=189040 https://bugs.chromium.org/p/chromium/issues/detail?id=581260 Is there a workaround for this issue or does getting a recent Webview working with the software renderer require quite some changes to the codebase? Many thanks!
,
Mar 28 2016
Yeah you still need gpu emulation on emulators, even if you want to run webview in software mode only. > Is there a workaround for this issue or does getting a recent Webview working with the software renderer require quite some changes to the codebase? It requires significant changes to the code base. And change will probably break frequently because we don't test on emulators at all. |
||
►
Sign in to add a comment |
||
Comment 1 by rsgav...@chromium.org
, Mar 28 2016