-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when reaching maximum number of linestrips #3075
Labels
🪳 bug
Something isn't working
💣 crash
crash, deadlock/freeze, do-no-start
🔺 re_renderer
affects re_renderer itself
Milestone
Comments
Wumpf
added
🪳 bug
Something isn't working
🔺 re_renderer
affects re_renderer itself
💣 crash
crash, deadlock/freeze, do-no-start
labels
Aug 22, 2023
3 tasks
Wumpf
added a commit
that referenced
this issue
Aug 25, 2023
### What * Fixes: #3075 * Related to: #3076 The second commit is the actual fix. But to avoid this family of crashes, the cpuwritegpuread belt now always does error checks and returns errors instead of paniking ### Checklist * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested [demo.rerun.io](https://demo.rerun.io/pr/3093) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/3093) - [Docs preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/examples) <!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://ref.rerun.io/dev/bench/) - [Wasm size tracking](https://ref.rerun.io/dev/sizes/)
jleibs
pushed a commit
that referenced
this issue
Aug 31, 2023
* Fixes: #3075 * Related to: #3076 The second commit is the actual fix. But to avoid this family of crashes, the cpuwritegpuread belt now always does error checks and returns errors instead of paniking * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested [demo.rerun.io](https://demo.rerun.io/pr/3093) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/3093) - [Docs preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/examples) <!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://ref.rerun.io/dev/bench/) - [Wasm size tracking](https://ref.rerun.io/dev/sizes/)
jleibs
pushed a commit
that referenced
this issue
Aug 31, 2023
* Fixes: #3075 * Related to: #3076 The second commit is the actual fix. But to avoid this family of crashes, the cpuwritegpuread belt now always does error checks and returns errors instead of paniking * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested [demo.rerun.io](https://demo.rerun.io/pr/3093) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/3093) - [Docs preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/examples) <!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://ref.rerun.io/dev/bench/) - [Wasm size tracking](https://ref.rerun.io/dev/sizes/)
jleibs
pushed a commit
that referenced
this issue
Aug 31, 2023
* Fixes: #3075 * Related to: #3076 The second commit is the actual fix. But to avoid this family of crashes, the cpuwritegpuread belt now always does error checks and returns errors instead of paniking * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested [demo.rerun.io](https://demo.rerun.io/pr/3093) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/3093) - [Docs preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/b6b737939d3219b0ca32e763d7276b5ca0d504ee/examples) <!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--><!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://ref.rerun.io/dev/bench/) - [Wasm size tracking](https://ref.rerun.io/dev/sizes/)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
🪳 bug
Something isn't working
💣 crash
crash, deadlock/freeze, do-no-start
🔺 re_renderer
affects re_renderer itself
re_renderer
crash #3070We're crashing right now when reaching the maximum number of linestrips.
There's likely similar cases still around - I remember fixing this for points in the past; should do a sweep over all of them, can we add a unit tests for this?
The penultimate fix for this is not having these limits in the first place which is a long standing issue #3076
The text was updated successfully, but these errors were encountered: