Actually, all the versions have the same debugging output. So I think this is just something kind of intermittent. I've put in some extra check code for this in an updated 1.010A prerelease, so hopefully that will permanently solve the issue. This would cause the AI to "go stupid" for a little while when these errors happen, so that could explain them sitting around and such when they otherwise should not be.
If you already downloaded the 1.010A version before now, please download it again to get this fix. I didn't feel like this one thing was worth a whole 1.010B version. Thanks for reporting it!