This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Don't initialize timestamps to TimePoint::min() #6979
Merged
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.
An alternative fix to #6747/#6667: In
FrameHistory::needsAnimation
, we are computingtime - previousTime
, but sincepreviousTime
was initialized toTimePoint::min()
, we got a integer overflow, which produced invalid values and made the map render continuously./cc @tobrun