Many thanks for reporting this. I've added a safeguard to prevent this in version 5.18, which I've just released.
