Apparently, the high cpu load stop when the upstart-event-bridge is stopped. This lends weight to the high cpu issue being caused the a kernel udev event issue (like bug 1234743).
However, what is not explained is why the Session Init retains the memory it consumes once the upstart-event-bridge is stopped.
Please would someone check to see if the issue is recreatable on grouper?
Apparently, the high cpu load stop when the upstart- event-bridge is stopped. This lends weight to the high cpu issue being caused the a kernel udev event issue (like bug 1234743).
However, what is not explained is why the Session Init retains the memory it consumes once the upstart- event-bridge is stopped.
Please would someone check to see if the issue is recreatable on grouper?