Sorry, there is nothing we can do about reports like this. Please see the bug report guidelines. We need reliable steps to reproduce the issue, and/or a .capx file demonstrating the issue. I don't see either of those here, so there's nothing I can do. Closing, please file a new issue with all the information we require.