Hi,
Thank you very much for the details!
This is a known issue with the recent release, luckily it affects a very small portion of installations with specific configurations. I logged in and applied a patch to the core plugin code to fix the issue.
Now it should be all right.
This fix will be added in the upcoming release of course.