I think that was a v1.0 bug, please try v1.1 (1.10.2 on the title screen bottom right corner); otherwise if you are on v1.1 and the error persists, is it consistent or just happens sometimes? I will give it a look regardless see what I can find
Thank you for reporting!