I haven't been able to reproduce this error, but in reviewing the code in this call stack we identified a possible case of thread interference, which could be the root cause of the ...