by bullock » Tue Oct 22, 2013 11:44 am
I'm hoping that version 10.0.22.0, now available for download, fixes this problem.
To help us learn more about what's going on, you've been running a special, diagnostic version the software that included some changes that could possibly have fixed the problem. You ran that version for a month and report that the problem has not recurred. It's not solid proof, but that test gives us some reason to believe that the error is finally fixed.
In any case, 10.0.22.0 includes those changes, and letting your coworkers run the newer version will quickly expose it to more extensive testing. If anyone observes the problem recurring with the newer version, please report it.
Regards.
Greg