Hello, welcome to the community! And thanks for reporting this.
This looks very similar to what was reported on this other thread, may I suggest that you watch the discussion there?
We identified the probable root cause of the issue and we should be able to make a development build available in the next few hours, with a fix for this issue.