Thanks for reporting this. We think we have fixed the issue and it will be included in the next update.