java.lang.NullPointerException at android.webkit.HTML5VideoFullScreen$2.surfaceDestroyed
Reported by
car...@instantbits.com,
May 1 2017
|
|||
Issue description
THIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE!
Device name: Multiple Samsung devices
Android version: 5, 6 and 7
WebView version (from system settings -> Apps -> Android System WebView): One user says they have the latest and I'm guessing most do.
Application: Web Video Caster
Application version: 4.1.7
URLs (if applicable): Don't know
Steps to reproduce: Don't know but they probably involve playing a video.
Expected result: The video should play and end without crashing.
Actual result:
I have only seen this through crashlytics and have one user that reported it but they didn't give me much information. The crash happens a lot with older devices and I thought it didn't happen on Android 5+ but it does. I can send you a link to the crashlytics report if you have a private way to do that. Here is the stacktrace:
Fatal Exception: java.lang.NullPointerException
at android.webkit.HTML5VideoFullScreen$2.surfaceDestroyed(HTML5VideoFullScreen.java:151)
at android.view.SurfaceView.updateWindow(SurfaceView.java:594)
at android.view.SurfaceView.onWindowVisibilityChanged(SurfaceView.java:239)
at android.view.View.dispatchWindowVisibilityChanged(View.java:8171)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:1113)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1357)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1128)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6269)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:791)
at android.view.Choreographer.doCallbacks(Choreographer.java:591)
at android.view.Choreographer.doFrame(Choreographer.java:561)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:777)
at android.os.Handler.handleCallback(Handler.java:730)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:176)
at android.app.ActivityThread.main(ActivityThread.java:5493)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1225)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1041)
at dalvik.system.NativeStart.main(NativeStart.java)
,
May 1 2017
This happens a lot more on devices with Android < 5 so it is really hard for me to narrow down on Crashlytics which devices it happens on that have Android 5+, or at least I don't know how to do it. I know it happens on one device with 5.0.1 and it is a SM-G3502L. Also Crashlytics says it only happens on Samsung devices. I do not know which video it happens with, or how to reproduce it. The stacktrace is pretty much all I have. If it helps I can share the Crashlytics crash report but I would rather send you that link in some private way.
,
May 1 2017
Thank you for providing more feedback. Adding requester "aluo@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 2 2017
The one user reporting the issue says he has the webview 57.0.2987.132
,
May 2 2017
android.webkit.HTML5VideoFullScreen is used by "classic" webview before switching to chromium webview in kitkat. So it's been deleted from aosp in kitkat. So I don't even know how a 5.0 device has that class unless samsung did a bad merge or something. Either way, can't do much about it here.
,
May 2 2017
Interesting. Thanks for the info. I have 5,6 and 7 devices reporting the error but way less than devices with Android < 5.
,
May 2 2017
Terrifying speculation: custom roms which restore the old webview because there's a bunch of people who were *really* upset that the new one doesn't support text reflow. :(
,
May 2 2017
Could be but strange that it is only on Samsung devices, however it could be that it is just one custom rom that targets Samsung devices. Ohh well. |
|||
►
Sign in to add a comment |
|||
Comment 1 by aluo@chromium.org
, May 1 2017