plugging-promise-race

A Promise.race leak in a JavaScript loop occurs when a reusable pool of promises accumulates .then handlers across iterations. Re-racing the same persistent pool causes handlers to build up, leading to memory leaks and unpredictable concurrency behavior.

Fix Promise.race leaks by refactoring your iterative loop to create a fresh per-iteration single-waiter signal. Awaiting this one-shot signal before the next iteration replaces persistent handler pools and prevents accumulation.

A per-iteration single-waiter signal is a fresh one-shot promise created during each loop iteration. It ensures only one handler waits per cycle, replacing reusable pools to stabilize worker loops and prevent cross-iteration handler accumulation.

Yes, the per-iteration single-waiter pattern applies to Promise.any and other short-circuiting constructs. Applying it to iterative concurrency loops ensures robust behavior by preventing the handler set from growing across iterations.

Constraints of single-waiter signals include specific failure modes and implementation limits inherent to short-circuiting constructs. Understanding these constraints ensures robust concurrency behavior and avoids unpredictable results in worker loops.