Ticket #157 (new defect)
omninames and nodebooter take 100% CPU during device startup
|Reported by:||balister||Owned by:||cdietric|
Omninames and nodebooter are taking 100% CPU during startup on a small form factor system.
I believe this is similar to a problem fixed during component startup where the framework polls omniNames to see when a device has started. On a high speed desktop, this is not noticeable, but on small systems the system spends so much time looking for the name, the device takes a long time to start up.
The (quick) solution is find the code in the device manager that starts the devices and insert a short sleep in the loop.