Comment 7 for bug 1403955

This issue is still a problem in 1.23, we just reproduced it.

Also, not sure why this bug was marked as fix released when there was no fix to release, just the assumption that this problem would not happen due to some new condition that doesn't seem to be met by our environment either. I think in this case the bug should have been marked either "invalid" or "not going to fix".