Crash output is below. The errors seem to be related to compositing. fsmauel@ can you look at the frame_sink_manager_impl.cc error below. What do you think can cause these?

Additionally, this test is running configuration 3 which is HW accelerated Android encode. I see there are many tests disabled on Android. braveyao@ can you take a look? Should we disable this test as well?

C  586.083s Main  [ERROR:program_binding.cc(232)] Error compiling shader: 
C  586.083s Main   shader program: #define TexCoordPrecision highp
C  586.083s Main  attribute TexCoordPrecision vec4 a_position;
C  586.083s Main  uniform mat4 matrix;
C  586.083s Main  varying TexCoordPrecision vec2 v_uvTexCoord;
C  586.083s Main  varying TexCoordPrecision vec2 v_yaTexCoord;
C  586.083s Main  attribute TexCoordPrecision vec2 a_texCoord;
C  586.083s Main  uniform TexCoordPrecision vec2 uvTexOffset;
C  586.083s Main  uniform TexCoordPrecision vec2 uvTexScale;
C  586.083s Main  uniform TexCoordPrecision vec2 yaTexOffset;
C  586.083s Main  uniform TexCoordPrecision vec2 yaTexScale;
C  586.083s Main  void main() {
C  586.083s Main    // Compute the position.
C  586.083s Main    vec4 pos = a_position;
C  586.083s Main    gl_Position = matrix * pos;
C  586.083s Main    // Compute texture coordinates.
C  586.083s Main    vec2 texCoord = a_texCoord;
C  586.083s Main    v_yaTexCoord = texCoord * yaTexScale + yaTexOffset;
C  586.083s Main    v_uvTexCoord = texCoord * uvTexScale + uvTexOffset;
C  586.083s Main  }
C  586.083s Main  
C  586.083s Main  [FATAL:frame_sink_manager_impl.cc(228)] Check failed: registered_sources_.count(source) == 0u (1 vs. 0)
C  586.083s Main  #00 0x7645f8c3 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x007528c3
C  586.083s Main  #01 0x76ed4c6b /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x011c7c6b
C  586.084s Main  #02 0x772abdc1 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x0159edc1
C  586.084s Main  #03 0x772abaab /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x0159eaab
C  586.084s Main  #04 0x772ac775 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x0159f775
C  586.084s Main  #05 0x770ea8f7 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x013dd8f7
C  586.084s Main  #06 0x770ea759 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x013dd759
C  586.084s Main  #07 0x760f55c1 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x003e85c1
C  586.084s Main  #08 0x7644f4c5 /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x007424c5
C  586.084s Main  #09 0x76465b7d /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x00758b7d
C  586.084s Main  #10 0x76465d6d /data/app-lib/org.chromium.content_browsertests_apk-1/lib_content_browsertests__library.so+0x00758d6d

Maybe it's similar to issue716691.

I'm not familiar with those tests. Leave it to experts.

Assigning to fsamuel@ waiting for feedback on #1.

@fsamuel are there any updates for this test disable?

I'm not sure why this bug was assigned to me to be honest. I'm marking as untriaged.

fsamuel@ you were probably targeted because of the command buffer-ish 
stack trace (error compiling shader etc), but that's very likely an
after effect of the test crashing the gpu process (the whole thing in
Android). This issue is also a dupe anyway.