... and it's after the scheduler has started :(I was really expecting it to be in early initialization. That would have made debugging it a lot easier.