I've never had that problem. I just upgraded to
2.0.0.6 last Saturday so if it's something in that version I probably haven't been using it long enough to detect the problem.

Sorry.