fix(framerate tracking): better handling of query failures #652
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.
Summary: improved handling of gl query errors that could cause failed queries to hang around in the pool and decrease frame time tracking accuracy
In some cases the query handling for frame deltas was not properly accounting for errors in the queries. This could lead to some old queries get left in the query pool for a long time, and warnings in the console about trying to start the same query multiple times, or fetching from a query that never started.
To address this, the main changes are: