Oops! Is this problem solved now?
This should be a bug with a low probability of occurring. I'll fix it in the next release!
