Comment 3 for bug 1461119

My guess is that this bug is happening because nodemgr builds a backlog of events when bombarded with lot of events in a short span of time. Root cause of that is nodemgr's processing of events at the rate of one event per sec (even though more events may be queued).