I've never experienced this issue but please update to latest version (1.611) and let me know if the issue still persists. If the issue persists, make sure to test with this extension disabled just to make sure it's the extension that is causing it.