Found this during performance optimizations. We always reinitialize
this to the correct value, so this wasn't caught in tests.