Webview test app crash on playing YouTube link

145 views
Skip to first unread message

sachin verma

unread,
Sep 24, 2020, 12:11:35 AM9/24/20
to andro...@googlegroups.com
Hi All, 

I am using android-x86 orieo build on this build I have to play YouTube URL link.
So I am able to open you link in webview test app. But on play video it's continuously cradhing. 

Below is log 

------- beginning of crash
09-01 06:49:43.039 2054 2051 F google-breakpad: -----BEGIN BREAKPAD MICRODUMP-----
09-01 06:49:43.039 2054 2051 F google-breakpad: V AndroidWebView:61.0.3163.98
....
09-01 06:49:42.675 1114 1455 E OMXNodeInstance: getExtensionIndex(0xf2521620:ffmpeg.vp9.decoder, OMX.google.android.index.enableAndroidNativeBuffers) ERROR: UnsupportedIndex(0x8000101a)
09-01 06:49:42.675 1943 2046 E ACodec : [OMX.ffmpeg.vp9.decoder] setPortMode on output to DynamicANWBuffer failed w/ err -1010
09-01 06:49:42.675 1114 1455 W OMXNodeInstance: [0xf2521620:ffmpeg.vp9.decoder] component does not support metadata mode; using fallback
09-01 06:49:42.676 1114 1455 E OMXNodeInstance: getParameter(0xf2521620:ffmpeg.vp9.decoder, ParamVideoAndroidVp8Encoder(0x6f600007)) ERROR: UnsupportedIndex(0x8000101a)
09-01 06:49:42.676 1114 1455 E OMXNodeInstance: getConfig(0xf2521620:ffmpeg.vp9.decoder, ConfigAndroidVendorExtension(0x6f100004)) ERROR: UnsupportedIndex(0x8000101a)

youtube_vm_crash.log[Another log just near crash]
-02 04:56:07.555 1204 1219 E ActivityManager: ANR in org.chromium.webview_shell (org.chromium.webview_shell/.WebViewBrowserActivity)
09-02 04:56:07.555 1204 1219 E ActivityManager: PID: 1946
09-02 04:56:07.555 1204 1219 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 7. Wait queue head age: 7577.7ms.)
09-02 04:56:07.555 1204 1219 E ActivityManager: Load: 1.94 / 1.19 / 0.49






sachin verma

unread,
Oct 8, 2020, 11:02:18 PM10/8/20
to andro...@googlegroups.com
Still waiting ....please any body check the isuse.

Thanks In Advance.
Sachin Verma

Michael Goffioul

unread,
Oct 9, 2020, 7:07:09 AM10/9/20
to Android-x86
There's not enough information to deduce anything. The errors reported by the OMX layer are expected and shouldn't be the cause of a crash.


--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CA%2BYOsKLrdZ5AEqRofzh_aqAi%2Bu%3DaV0FOqVjPN7dn1ipV%3DnUPFQ%40mail.gmail.com.

Mauro Rossi

unread,
Oct 9, 2020, 3:04:17 PM10/9/20
to Android-x86
Hi,
please check in the logcat if you see some SIGABRT section and provide /data/log.txt in compressed format

11-30 12:14:35.848  2101  2603 F libc    : Fatal signal 6 (SIGABRT)
Reply all
Reply to author
Forward
0 new messages