fleet-plugging-promise-race

Promise.race leaks memory across iterations because reused persistent promises accumulate handlers. Replacing the promise pool with a fresh per-iteration signal eliminates this handler buildup and ensures correct concurrency semantics.

You prevent promise handler accumulation by implementing a single-waiter pattern that replaces the persistent promise pool with a fresh, replaceable signal awaited during each iterative loop cycle.

A single-waiter pattern for JavaScript concurrency control replaces a pool of long-lived promises with a replaceable signal, ensuring each loop iteration awaits a fresh promise to prevent cross-iteration leakage.

Yes, Promise.any suffers from the same cross-iteration handler leaks when reusing long-lived promises across iterative tasks. Applying a fresh per-iteration signal prevents the handler accumulation that causes these leaks.

You implement safe iterative concurrency limits by replacing persistent promise pools with a single-waiter signal, ensuring every loop cycle awaits a fresh promise instead of reusing a shared pool of tasks.