I can't reproduce locally, but seems to be caused by my patch to not call committedLoad twice. Given I cannot reproduce locally, I decided to skip, and open a bug report instead so we can investigate.
I end up reverting the whole thing.
Bug references and revision numbers are useful for those of us in the peanut gallery. ;)
After investigating with eseidel, and joanie, we found out the problem - this wasn't caused by my patch after all, but it's still weird why it showed up out of nowhere.
Should be fixed in r53111.