Closed computablee closed 11 months ago
This is also an issue with the schedulers, where if a loop goes near int.MaxValue
the internal counters will overflow and the mechanism by which parallel-for loops terminate is rendered impossible. Checks need to be implemented for this to avoid halting issues.
Describe the bug.
When a parallel-for loop (namely collapsed loops) exceed
int.MaxValue
iterations, there is some sort of internal overflow that is uncaught and loop results become invalid.To Reproduce.
Example:
Expected behavior.
Either some sort of overflow exception, or optimally, an internal refactor to migrate to
long
instead ofint
for loop scheduling. Might be good for a v2.0.0 release.Desktop (please complete the following information):