Thanks for the report, and sorry for the delayed response. We just had a chance to investigate this further and a fix will be in the v6.0.4 release, due out later this week.
We appreciate the feedback, as always, and hope the new release gets you fixed up!
Thanks,
Alex