This problem has been fixed in the 1.01.2 release, now available for download.

Just as a note, the challenge in tracking down this problem is that is only happened on computers that had been running for 25 days or more.

Thanks to everyone who helped us get to the bottom of the problem.