Steps to reproduce the problem:
1. Set up a WebRTC call between Windows Desktop and Android device with captured/sent video resolution higher than 320x240
2. Observe the Android browser and see that the received video track is either not rendered at all or freezes very soon.
1. Connect call at low 320x240 resolution and confirm all is OK.
2. Screen share from Desktop at high res low frame rate (1280x720@5fps)
3. Observe Android browser is unresponsive and sharing is not displayed.
What is the expected behavior?
Standard 640x480 or higher video tracks should decode and render well on recent Android devices.
What went wrong?
The Android browser becomes unresponsive Chrome error sequence is report on device connected to Android Device Monitor:
ERROR:gles2_cmd_decoder.cc(5332)] Error: 5 for Command kSwapBuffers
ERROR:gles2_cmd_decoder.cc(15702)] Context lost because SwapBuffers failed.
ERROR:gles2_cmd_decoder.cc(4325)] GLES2DecoderImpl: Trying to make lost context current.
Generally this continues as long as the video track is being received, but in a few tests, it did recover.
Did this work before? Yes Works on Android 5.1.1 Samsung Tablet with same Chrome Version.
Chrome version: 61.0.3163.98 Channel: stable
OS Version: 7.0
Error is reproducible on Android 7.0 and 6.01 on
Galaxy S7/S7 Edge, HTC 10, Pixel, Nexus 5 devices