Thanks for the report!
The issue should be resolved with the 1.4.1 patch.
If you see it happen again at any point, please let us know.
The issue should be resolved with the 1.4.1 patch.
If you see it happen again at any point, please let us know.