Thanks for the report, I think we identified what may be causing that bug. It'll be fixed in the next update.
