We have identified the problem, it occurred in a very rare condition, but thanks to the detailed report of @mark1 we were able to track it down and it will be fully solved in the next update.
We have identified the problem, it occurred in a very rare condition, but thanks to the detailed report of @mark1 we were able to track it down and it will be fully solved in the next update.