New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 602210 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Green video frame blinks during tab closing

Reported by lo...@yandex-team.ru, Apr 11 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2706.0 Safari/537.36

Steps to reproduce the problem:
1. Open tab with 60 fps video. ( https://www.youtube.com/watch?v=0GR-96fasA8 )
2. Close tab.
3. Repeat 10 times.

What is the expected behavior?
Tab is closed without artefacts.

What went wrong?
Green video frame blinks.

In chrome://gpu errors:
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(14683)] : [.CommandBufferContext.DisplayCompositor-0659C310]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(14683)] : [.CommandBufferContext.DisplayCompositor-0659C310]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(14683)] : [.CommandBufferContext.DisplayCompositor-0659C310]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(7857)] : [.CommandBufferContext.DisplayCompositor-0659C310]RENDER WARNING: texture bound to texture unit 1 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(7857)] : [.CommandBufferContext.DisplayCompositor-0659C310]RENDER WARNING: texture bound to texture unit 2 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[11332:5444:0411/120636:ERROR:gles2_cmd_decoder.cc(7857)] : [.CommandBufferContext.DisplayCompositor-0659C310]RENDER WARNING: texture bound to texture unit 3 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

Did this work before? No 

Chrome version: 52.0.2706.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

I has investigated the problem.
It is race condition.
1) Renderer process creates texture in GPU process with video frame and get id.
2) Renderer creates quad with this id and transfers it to Browser process for compositing.
3) Renderer dies.
4) GPU closes GpuChannel and deletes all Renderer's textures.
5) Browser generates command for GPU to draw quad with texture id.
6) GPU doesn't find texture, makes error log and draws video quad with null-texture (YUV-to-RGB => green frame).
 
Cc: danakj@chromium.org enne@chromium.org

Comment 2 by danakj@chromium.org, Apr 12 2016

Cc: piman@chromium.org jbau...@chromium.org
This is similar to bugs where on chromeos we would show black during window close animations. People have failed to keep the renderer alive until the tab is no longer shown so far in that scenario.

But there's no animation on windows, not sure why we're showing the tab after the renderer is killed already. Who would know more?
Components: Blink
Components: -Blink Blink>Compositing
Components: -Blink>Compositing Internals>Compositing
Cc: vmi...@chromium.org sunn...@chromium.org ericrk@chromium.org
Labels: Needs-TestConfirmation
Could TE please confirm if this is reproducible?
Cc: kkaluri@chromium.org
Labels: -Needs-TestConfirmation
Unable to reproduce the issue on Windows 10 with chrome Stable #52.0.2706.0, Canary #60.0.3090.0

These are the steps followed.

1. Opened tab with url https://www.youtube.com/watch?v=0GR-96fasA8
2. Close tab.
3. Repeat 10-15 times.

Didn't observe any green artifacts while closing the tab.
Attaching a screen-cast for reference.
Thank You... 
602210.mp4
12.8 MB View Download
lof84: Does this still reproduce for you?
60.0.3096: OK.
I think we can close this bug.
Status: WontFix (was: Unconfirmed)
lof84@, Thank you for the update. Please feel free to file a new bug for any further issues with chrome in future.

Sign in to add a comment