Given that we've implemented the only known solution for this in bug 1877075, the remaining explanation for it might not be thread-related. Some kind of memory corruption (even single threaded) could have the same effect.
Given that we've implemented the only known solution for this in bug 1877075, the remaining explanation for it might not be thread-related. Some kind of memory corruption (even single threaded) could have the same effect.