Comment 3 for bug 1189850

It's the read-read optimisation that was re-enabled. Not sure where the root cause is as reproducing it reliably and quickly is tricky.