Bugfix/22 improve timer thread usage #23
Merged
Conversation
This file contains 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
|
@amarqueslee Thank you for your work! I've just merged your PR. This PR fixes the possibility that multiple threads can be spawned and runs in parallel. Again, I appreciate your investigation and proposals! |
This was referenced Feb 22, 2018
Sign up for free
to 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.
This is my first draft at nailing down the tick thread logic, as discussed in issue #17 . I essentially went ahead and tried out the proposal I put forward in corresponding issue #22 .
I tested it and - dare I say it - it works for me. My testing involved opening a tall file, scrolling up/down for a bit, and issuing an
echo timer_info()at various intervals to check for leaks. The command consistently returned[]so I think it's good.