We've located some code that may be causing the issue and should try to fix it tomorrow. Because we have not been able to find a stable way to reproduce the BUG so far, we will try as soon as possible to see if we can solve this problem for everyone.