D146877 could be one workaround. It wait video frame complete. And calling the Synchronize() without using compositor device for video decoding might be another workaround. It seems less risky than D146877.
Bug 1766684 Comment 23 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
D146877 could be one workaround. It wait video frame complete. And calling the Synchronize() without using compositor device for video decoding might be another workaround. It seems less risky than [D146877](https://phabricator.services.mozilla.com/D146877).
[D146877](https://phabricator.services.mozilla.com/D146877) could be one workaround. It wait video frame complete. And calling the Synchronize() without using compositor device for video decoding might be another workaround. It seems less risky than [D146877](https://phabricator.services.mozilla.com/D146877).
[D146877](https://phabricator.services.mozilla.com/D146877) could be one workaround. It waits video frame copy complete. And calling the Synchronize() without using compositor device for video decoding might be another workaround. It seems less risky than [D146877](https://phabricator.services.mozilla.com/D146877).
[D146877](https://phabricator.services.mozilla.com/D146877) could be one workaround. It waits a video frame copy complete. And calling the Synchronize() without using compositor device for video decoding might be another workaround. It seems less risky than [D146877](https://phabricator.services.mozilla.com/D146877).