Skip to content
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
merged 2 commits into from
Nov 9, 2016

Conversation

kkaefer
Copy link
Member

@kkaefer kkaefer commented Nov 9, 2016

An alternative fix to #6747/#6667: In FrameHistory::needsAnimation, we are computing time - previousTime, but since previousTime was initialized to TimePoint::min(), we got a integer overflow, which produced invalid values and made the map render continuously.

/cc @tobrun

…flows

In FrameHistory::needsAnimation, we are computing "time - previousTime", but since previousTime was
initialized to Duration::min(), we got a integer overflow, which produced invalid values.
…down

This is to test that continuous mode stops rerendering once no further changes are needed, i.e. to test the absence of "busy rendering".
@mention-bot
Copy link

@kkaefer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ansis, @jfirebaugh and @tmpsantos to be potential reviewers.

@tobrun
Copy link
Member

tobrun commented Nov 9, 2016

Works great, both CPU monitor as tests confirm.

screen shot 2016-11-09 at 17 30 20

Thank you for picking this up!

@kkaefer kkaefer merged commit 16def03 into master Nov 9, 2016
@kkaefer kkaefer deleted the 6979-dont-initialize-timestamps-to-timepoint-min branch November 9, 2016 16:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants