Thanks for checking. I assume it happens fairly often then, just weird that it has not been reported elsewhere. I think I have fixed it in the source, so it will be part of the next release.
The fix is already in 2.1.0.107 if you are OK with running an experimental version.