Comment 16 for bug 1770929

The 0.8-series was affected by this (as I mentioned above, fixing the underlying problem avoids this error and a number of these have been fixed, so it is harder to trigger).

I have just proposed a fix for it be merged into the 0.8-series:

I would still appreciate any feedback on the 0.7-series branch above. I am more nervous about making changes in our stable branch without feedback.