Skip to content

Postprocessor shutdown no longer kills the post-processor thread. - #68

Merged
OldUser101 merged 2 commits into
masterfrom
fix/postprocessor-shutdown
Nov 2, 2026
Merged

OldUser101 merged 2 commits into
masterfrom
fix/postprocessor-shutdown

Conversation

@shardros

Copy link
Copy Markdown
Member

Any code that crashed after creating a Camera never exited. One bad frame also killed the post-processor thread silently, after which every capture() stalled for 1s.

  • vision: don't let the postprocessor keep the process alive
  • vision: keep the postprocessor alive when a frame fails

shardros and others added 2 commits October 31, 2026 17:54
The thread is only stopped by `Camera.__del__`, but Python waits for non-daemon
threads before it destroys objects, so usercode which crashed after creating a
`Camera` never exited.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Any exception ended the thread silently. The queue then filled up, the preview
stopped updating and every `C.capture()` blocked for a further second.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shardros shardros changed the title fix/postprocessor shutdown Postprocessor shutdown no longer kills the post-processor thread. Oct 31, 2026
@shardros
shardros requested a review from OldUser101 October 31, 2026 18:47
@OldUser101
OldUser101 merged commit 38d7018 into master Nov 2, 2026
1 check passed
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