So far in version 0.199.497 this bug has not been seen so this is probably fixed.
The sector that was loaded that caused or has this issue: