Fixed freeze in the polling loop#1688
Merged
aleksandr-voitenko merged 1 commit intostagingfrom May 6, 2026
Merged
Conversation
sandboxcoder
approved these changes
May 6, 2026
summeroff
approved these changes
May 6, 2026
This file contains hidden or 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
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.
Description
This PR fixes a rare freeze/stall condition in OBS client polling workers caused by millisecond sleep arithmetic underflowing when a poll cycle takes longer than the configured interval.
Motivation and Context
In
worker-signals.hppand similarly innodeobs_service.cppthe loop does roughly:The intent is fine:
The bug appears when the work takes longer than the target interval:
But
totalSleepMSis declared assize_t, which is unsigned. A negative value assigned to an unsigned integer wraps to a huge positive value. On a 64-bit build, -47 can become something like:18446744073709551569A minimal program that reproduces the issue looks like this:
How Has This Been Tested?
Separate minimal test program.
Types of changes