fix: enforce minimum debounce of 10ms to prevent CPU exhaustion #85
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 addresses an issue where setting
watch_debounce_msto 0 caused 100% CPU usage due to a tight polling loop. A minimum debounce value of 10ms is now enforced to prevent this denial of service condition.Fix
set_watch_debounceinsrc/config.rsto reject values less than 10ms.Testing
vgrep config set watch-debounce 0now fails with "Watch debounce must be at least 10ms".