that is indeed weird. I looked at the code more closely and there could be a race condition to cause what you see. but first of all even if that race condition triggers, it would only cause the error to happen once and can recover from that. secondly, a race condition won't behave so consistently across multiple installs.
in any case I'll put in a check to make it more robust. I can't guarantee it will solve your problem but it's worth a shot. please wait for the next release which is beta5, dude late November. sorry I can't think of anything else we can do for your issue. |