Increase DEFAULT_BUFFER_LOCK_GET_TIMEOUT to 3s#204
Merged
ayufan merged 1 commit intoayufan:mainfrom Mar 2, 2026
Merged
Conversation
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
2 participants
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 PR increases the
DEFAULT_BUFFER_LOCK_GET_TIMEOUTconstant to 3 seconds to prevent the HTTP 500 "No frames" error when stale detection triggers and restarts the camera.3 seconds is sufficient to allow the first frame to be served after restart with the 3 cheap USB cameras I tested with. I have no idea if more is needed for poorer cameras.
Further details are available in the discussion in PR #200 thread.