This started to happen in the vicinity of r83552
We haven't been able to reproduce this so far, but issue 58306 is likely related.
This hasn't happened in many many runs, so marking fixed.