event loop starvation

When the event loop can never move on because code keeps scheduling more immediate work, so timers and I/O are never handled.

In more detail

Recursive process.nextTick() calls, or promises that keep queuing more promises, cause it because those queues are always emptied first. Using setImmediate() for recurring work lets the loop complete a full turn between steps.

Related terms

Taught in

References