We do not need to account for drift when we USE_WINDOWS_EVENTS#1666
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
pierreluctg changed the title 
CollaboratorAuthor
pierreluctg commented Sep 29, 2023
@zariiii9003 please review |
Uh oh!
There was an error while loading. Please reload this page.
zariiii9003 approved these changes Oct 2, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using USE_WINDOWS_EVENTS the waitable timer will be fired at fixed rate, we do not need to account for the drift.
The change makes it wait for the timer to be in signaled state only.
Previous code was causing multiple frames to be send back to back without delay.