Thanks a lot for this report; this had never happened to us before, and it's a very serious issue. It has now been located and fixed, and I'll likely upload the new version today with this fix, plus other fixes and improvements.
