Your comments

Happened to me especially since 0.4.8

"This should have been fixed in version 0.4.4b. Is that the version you are using?"


It's not!