I'm not a fan of many time-based processes interacting in unknown ways... Also, GLES2Implmentation is used on threads that don't have a message loop so posting a task for the timeout is not generally possible.

Among others we have a facility to flush the command buffer after some time when inserting commands (see CommandBufferHelper::PeriodicFlushCheck), but it is not enabled for compositor/worker contexts because it was counter-productive at the time - we can certainly revisit if we see it helps.

Are there specific problems you want to addressed with a timeout-based flush? As opposed to the callers flushing when they need to?

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

sunnyps@, is this something still worth looking into?

jdarpnian@ has been looking into command buffer performance recently for fixing specific webgl pages that are slow. Unless there's a specific case that would benefit, this is probably a WontFix.