unlike our sleeping decoder thread whose shut down may be delayed, these processes put a lot of resource strain on the system
zombie processes may stay up indefinitely until we wait for their result
This unfortunately can reintroduce hickups on seeking backwards. This is more telling about our poor decode strategy for backward seeks than anything else. Something we'll have to tackle in the near future.
What
There's two critical issues leading up to this:
waitfor their resultThis unfortunately can reintroduce hickups on seeking backwards. This is more telling about our poor decode strategy for backward seeks than anything else. Something we'll have to tackle in the near future.
Checklist
[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):
mainbuild: rerun.io/viewernightlybuild: rerun.io/viewer[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in
CHANGELOG.mdand the migration guidePR Build Summary
Recent benchmark results
Wasm size tracking
To run all checks from
main, comment on the PR with@rerun-bot full-check.