Conversation
trisyoungs
approved these changes
May 8, 2026
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.
I tracked down the source of my Array3D issues. It is a legitimate bug, but it only gets triggered when performing a parallel iteration. Even then, it depends on how TBB decides to split the work. On most machines, TBB splits into a few different threads on the array's Z-axis, so the bug isn't triggered. On my machine, for whatever reason, TBB decided to split into a thousand different threads that didn't even respect the Y-axis boundaries, so it created the weird conditions where the bug could be triggered.
The good news is that my testing mostly shows that this is a crash-to-desktop style bug, not a silently-produce-wrong-data bug, so I am probably the only person who ever experienced it.