Comment 1 for bug 1795195

It's a little bit random as it's an accessing-freed-memory bug.

5.0 has the same logic, and so should be vulnerable even if it doesn't usually happen.