Comment 27 for bug 1007082

Right, thinking of it, it might be that it was actually the issue that is now solved (no more bad page state) but now running into bug #1011792. At least this other bug now has a reproducer that does not require a production load.