It’s probably the same issue as reported in this thread. Hope we’ll soon find a solution for this bug that I can’t reproduce (yet?).