Thanks for both of your reports, this was due to some timing issues with multiple threads and should be fixed now in 10.5.1.2.
Thanks for both of your reports, this was due to some timing issues with multiple threads and should be fixed now in 10.5.1.2.