Works fine in Chrome 64.0.3265.0/CrOS 10127.0.0 - Candy

Unable to reproduce the issue on 64.0.3270.0/ 10134.0.0 - Kip

Issue observed for all VP8 and VP9 videos. Try any video from  http://crosvideo.appspot.com/ 

Issue also observed by disabling the H/W decode.

Feedback report from candy device: 84663574557
Issue not repo on squwaks device.

Is this only happening on Candy?

As of now it is observed only on candy device. Not reproduced on other device on squawks, kip, daisy, reks, blaze, elm and few newer device.

Will try on few other baytrail devices and updated if reproduced.

Observed issue on ninja device. 

observed on butterfly device, dev channel.

May I ask for a confirmation please, per #4, this happens for VP8 and VP9 videos, but not H264? Thank you.

I can reproduce the issue on Butterfly and it is only on VP9 and VP8. 

Actually, it only happens on SW decoding path. If I turn the hw decoding off, the issue can be reproduced with h264 videos.

There are several GL errors in the log.

=============
[5546:5546:1120/141301.584839:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.600982:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.606143:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.618348:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.622700:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.636967:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.638998:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.655836:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.669943:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.688923:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.702832:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.720592:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.737056:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.756324:ERROR:gles2_cmd_decoder.cc(9986)] [.DisplayCompositor-0x2695f1f2e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[5546:5546:1120/141301.799739:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.799877:ERROR:gles2_cmd_decoder.cc(18372)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glReleaseTexImage2DCHROMIUM: no image found with the given ID
[5546:5546:1120/141301.799930:ERROR:gles2_cmd_decoder.cc(18322)] [.Media-0x2a16b26bd600]GL ERROR :GL_INVALID_OPERATION : glBindTexImage2DCHROMIUM: no image found with the given ID

Deleted: chrome.txt 59.4 KB

chrome.txt 59.4 KB View Download

Dale. Can you take a look? Thanks.

Should have been fixed by issue 786059, but something still seems wrong.

Issue 787028 has been merged into this issue.

64.0.3274.0 on Link shows this behavior still.

Not related to my changes then. I don't have the hardware to do a bisect for this, can someone from CrOS take a look?

+dcastagna since this should be using GpuMemoryBuffers if it's software decoded Vp8/Vp9, which I think it is on Link.

jvernon@ are you able to capture a log of chrome://gpu -- it's possible we have a separate issue here.

Assigning to dcastagna according to #19.

#20 - Here you go. Attaching the file wasn't working, so Drive link it is...

https://drive.google.com/a/google.com/file/d/1yUStBEjsZL9Jcu2amtLJW3sZFUBFQGmH/view?usp=sharing

Seems the command buffer doesn't like the textures we're generating for software decoding for some reason. If you're able to append switches to startup, can you try running with "--disable-gpu-memory-buffer-video-frames"

Just rebooted and it picked up an update to 64.0.3280.5 

Now I can't reproduce the issue. 

Sorry for the fire-drill. If I see this again, I'll collect logs and open a new crbug.

Is it possible this was caused by switching to NV12 on intel?
That patch has been already reverted because of crbug.com/786842, that would explain why in the new update it can't be reproduced.

can we remove this as dev blocker if can no longer reproduce per #24?

Marking this as fixed since we reverted the NV12 CL in 64.
 crbug.com/791676  to investigate the regression.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-64; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-64 label, otherwise remove Merge-TBD label. Thanks.

Verified on candy on 10176.5.0, 64.0.3282.11