Calling Android APIs which are not available on KitKat in browser_tests |
||
Issue descriptionWe have android-kitkat-arm-rel bot which runs browser_tests on KitKat. When we set a ContentBrowserClient via SetBrowserClientForTesting(), we somehow call Android APIs which are only available from Lollipop. F/libc ( 4994): Fatal signal 6 (SIGABRT) at 0x00001382 (code=-6), thread 5009 (ChildProcessMai) I/dalvikvm( 4978): Could not find method android.media.MediaCodecInfo$CodecCapabilities.getVideoCapabilities, referenced from method org.chromium.media.MediaCodecUtil.a ddVp9CodecProfileLevels W/dalvikvm( 4978): VFY: unable to resolve virtual method 327: Landroid/media/MediaCodecInfo$CodecCapabilities;.getVideoCapabilities ()Landroid/media/MediaCodecInfo$Vide oCapabilities; I've noticed this while working on https://chromium-review.googlesource.com/c/chromium/src/+/1130967
,
Jul 17
It seems like we only call getVideoCapabilities() in addVp9CodecProfileLevels(). This means that we somehow enter this condition: https://cs.chromium.org/chromium/src/media/base/android/java/src/org/chromium/media/MediaCodecUtil.java?l=255, which shouldn't be possible if we are on kikkat. Are these tests running on emulators or physical devices?
,
Jul 19
I ran the test on my Nexus 5 device. I think that we are using physical devices on trybots too.
,
Aug 2
|
||
►
Sign in to add a comment |
||
Comment 1 by bashi@chromium.org
, Jul 17Status: Available (was: Untriaged)