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

Issue 775247 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ jjyla...@mozilla.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Querying COMPILE_STATUS bypasses shader cache

Project Member Reported by kainino@chromium.org, Oct 16 2017 
If a WebGL application queries the COMPILE_STATUS of a WebGLShader, it seems to bypass the shader cache and compile the shader even if it's been compiled on a previous load:
https://cs.chromium.org/chromium/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?l=10699&rcl=77a9952fa36514bbb2ea06a3eb291a7dd42ee1a5

This is probably affecting many (if not most) WebGL applications out there.

(I thought there was already a crbug for this but I can't find it anywhere.)

Comment 1 by kainino@chromium.org, Oct 16 2017

Components: Internals>GPU
I think I tested this but I'm not sure, so I might be wrong about the behavior here. But at a glance it looks like that's what's happening.
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 17

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by kbr@chromium.org, Oct 18

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
►

Sign in to add a comment