Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement callback based timers without relying on a task. Fixes #86. #98

Merged
merged 3 commits into from
Oct 27, 2018

Conversation

s-ludwig
Copy link
Member

In the previous implementation, the callback tasks were starving as soon as the last external reference to a non-pending timer was given up.

In the previous implementation, the callback tasks were starving as soon as the last external reference to a non-pending timer was given up.
@s-ludwig s-ludwig merged commit ec170e9 into master Oct 27, 2018
@s-ludwig s-ludwig deleted the issue-86-timer-memory-leak branch October 27, 2018 18:12
s-ludwig added a commit that referenced this pull request Mar 11, 2021
This fixes a regression introduced by #98 and 03ffe70, which lead to a new independent task being created per timer invocation instead of invoking the callbacks in a single loop.
gedaiu pushed a commit to gedaiu/vibe-core that referenced this pull request Apr 2, 2021
This fixes a regression introduced by vibe-d#98 and 03ffe70, which lead to a new independent task being created per timer invocation instead of invoking the callbacks in a single loop.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants