This should be fixed in the latest patch (1.2.10). Let me know if it still happens so that I can take another look.