I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there.
We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace.
I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there.
We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace.