Since the registration code is concurrently run in a thread pool, the order in which components register with the component updater is non-deterministic.

It is unclear what the impact of this is. However, there was an implementation intention to register components in the order of their relative priority, and this implementation has been broken once the registration of components has been changed to use the new task scheduler API.