This should be fixed in v1.5.3 b5172.
There is now an option to disable the feature that causes this issue:
