I'm going to bet that this is related to bug 1080765, and since we probably don't have access to the original machines on which this was happening, I'll close this issue.
I'm going to bet that this is related to bug 1080765, and since we probably don't have access to the original machines on which this was happening, I'll close this issue.