This should be fixed in the version currently pending for review (2.0.131.1). Personally, I have never been able to reproduce this issue, but I'm confident the next version will fix it.