Comment 32 for bug 1537585

This only appears to happen when the transaction system is under load. Observations include when updating the supported containers for the machine during setting the machine addresses. Since there are two different transaction operations targeting the same document, weirdness ensues.

Still investigating the weirdness, but this does explain the intermittent nature of the issue.