Issue metadata
Sign in to add a comment
|
WebView crash in Android P: couldn't find "libmonochrome.so"
Reported by
vivanko...@counterpath.com,
Apr 25 2018
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. 2. 3. What is the expected behavior? What went wrong? Caused by: android.util.AndroidRuntimeException: java.lang.reflect.InvocationTargetException at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:274) at android.webkit.WebView.getFactory(WebView.java:2648) at android.webkit.WebView.ensureProviderCreated(WebView.java:2643) at android.webkit.WebView.setOverScrollMode(WebView.java:2708) at android.view.View.<init>(View.java:4792) at android.view.View.<init>(View.java:4932) at android.view.ViewGroup.<init>(ViewGroup.java:654) at android.widget.AbsoluteLayout.<init>(AbsoluteLayout.java:55) at android.webkit.WebView.<init>(WebView.java:659) at android.webkit.WebView.<init>(WebView.java:604) at android.webkit.WebView.<init>(WebView.java:587) at android.webkit.WebView.<init>(WebView.java:574) ... 35 more Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Method.invoke(Native Method) at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:269) ... 46 more Caused by: java.lang.RuntimeException: Cannot load WebView at com.android.webview.chromium.WebViewChromiumFactoryProvider.I(WebViewChromiumFactoryProvider.java:78) at com.android.webview.chromium.WebViewChromiumFactoryProvider.<init>(WebViewChromiumFactoryProvider.java:36) at com.android.webview.chromium.WebViewChromiumFactoryProviderForP.<init>(WebViewChromiumFactoryProviderForP.java:4) at com.android.webview.chromium.WebViewChromiumFactoryProviderForP.create(WebViewChromiumFactoryProviderForP.java:1) ... 48 more Caused by: org.chromium.base.library_loader.ProcessInitException at org.chromium.base.library_loader.LibraryLoader.loadAlreadyLocked(LibraryLoader.java:100) at org.chromium.base.library_loader.LibraryLoader.loadNowOverrideApplicationContext(LibraryLoader.java:35) at com.android.webview.chromium.WebViewChromiumFactoryProvider.I(WebViewChromiumFactoryProvider.java:70) ... 51 more Caused by: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/Chrome/Chrome.apk"],nativeLibraryDirectories=[/system/app/Chrome/lib/arm64, /system/lib, /system/lib]]] couldn't find "libmonochrome.so" at java.lang.Runtime.loadLibrary0(Runtime.java:1012) at java.lang.System.loadLibrary(System.java:1657) at org.chromium.base.library_loader.LibraryLoader.loadAlreadyLocked(LibraryLoader.java:66) ... 53 more Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: Channel: n/a OS Version: Flash Version:
,
Apr 26 2018
,
Apr 26 2018
if this is a transient user-reported issue, then it's probably caused by the application starting while webview is being updated. If you can consistently reproduce it on on your device, we need more information; specifically a bugreport taken from the device immediately after the crash.
,
Apr 27 2018
Yes, this a user reported issue. If webview is being updated, how can that be properly handled?
,
Apr 27 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2018
This is unlikely to be a webview update (it's technically possible but the time window for it to fail in this exact way is extremely narrow) This happens on the P developer preview I assume from the bug title: if so this is almost certainly actually an actual android bug b/74357697 which is fixed in later versions of P. Workaround is to uninstall chrome updates on the device (the current chrome update that the play store installs is not actually compatible with P and the mechanism that's intended to deal with that case and fall back to something working got broken). The next developer preview/beta/whatever is released, along with the final public version, will not have a problem here, as the fix landed some time ago. Separately: don't attempt to handle the case where the webview is being updated. It's a transient state and users will be fine in a minute or two (much less in later OS versions; the time window has been reduced). Handling it properly is probably impossible because of how package updates work in android, and attempting might result in worse behaviour. It's, unfortunately, best to just let the app crash; by the time the user launches it again the update will be over and it'll work.
,
Apr 30 2018
Thanks for your feedback and explanation. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vivanko...@counterpath.com
, Apr 25 2018