Block commit or BeginMainFrame until SwapAck for low memory devices |
||||||
Issue descriptionThere is existing logic (see "commit_completion_waits_for_activation_") that blocks the main thread on commit until activation for WebGL and Canvas. To force double buffering, we can extend that logic so it blocks until we get a swap ack with the previous resources back. It would be relatively easy to implement, but would proactively block before the first non-deferrable draw command; if the app uses RAF like it should, we would block the main thread unnecessarily - but that might be okay for low end devices. Alternatively, we could throttle the next BeginMainFrame until the SwapAck, which would free up the main thread and should work just as well for RAF based content.
,
Apr 10 2017
We can try experimenting with single thread proxy and commit to active tree for such cases.
,
Apr 11 2017
,
Jun 5 2017
Hey Andrew - what's the plan? When can we expect an update here?
,
Jun 6 2018
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
,
Jun 29 2018
sunnyps@, are we still interested in experimenting with this?
,
Jun 29 2018
What would be the end user benefit on low end devices?
,
Jul 25
,
Aug 15
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by briander...@chromium.org
, Apr 10 2017