Thanks for the report. We have heard of this before, but did not investigate further:
I created a github issue to track the bug.