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

Linux Platform: fix the dispatch thread #135

Merged
merged 1 commit into from
Feb 21, 2025
Merged

Conversation

GwendalRaoul
Copy link
Contributor

In fact since a40af2f an old bug is now visible resulting in a 100% cpu usage.
In case we exit the wait, if there is nothing in the queue, we must not release the lock as we are waiting again immediately.

In fact since a40af2f an old bug is now
visible resulting in a 100% cpu usage.
In case we exit the wait, if there is nothing in the queue, we must not release the lock
as we are waiting again immediatelly.
@GwendalRaoul GwendalRaoul merged commit 6a435a3 into master Feb 21, 2025
3 checks passed
@GwendalRaoul GwendalRaoul deleted the fix/do_not_unlock branch February 21, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants