JavaScript Async Lifetimes: The Leak You Have and Probably Do Not Know About

class DatabaseConnection {
  constructor(private conn: Connection) {}

  async query<T>(sql: string, params: unknown[]): Promise<T> {
    return this.conn.execute(sql, params);
  }

  async [Symbol.asyncDispose]() {
    await this.conn.close();
  }
}

async function getUser(id: string) {
  await using db = new DatabaseConnection(await pool.acquire());
  // the connection releases when this block exits, always
  return db.query('SELECT * FROM users WHERE id = ?', [id]);
}

on:

async function withCleanup() {
  await using stack = new AsyncDisposableStack();
  const conn = stack.use(await openConnection());
  stack.defer(async () => await logCompletion());
  // both cleanup when block exits, in reverse registration order
  return conn.query('...');
}

AbortSignal.any() for Composed Cancellation

Combines multiple cancellation sources into a single signal. Fires immediately when any input signal triggers, with the reason property indicating the source.

const controller = new AbortController();
const timeoutSignal = AbortSignal.timeout(5000);
const combined = AbortSignal.any([controller.signal, timeoutSignal]);

const response = await fetch(url, { signal: combined });

Building a Task Scope

Combining these primitives creates a reusable lifecycle boundary:

class TaskScope {
  private controller = new AbortController();
  readonly signal = this.controller.signal;
  private tasks: Promise<unknown>[] = [];

  spawn<T>(fn: (signal: AbortSignal) => Promise<T>): Promise<T> {
    const task = fn(this.signal).catch((err) => {
      if (err.name !== 'AbortError') this.controller.abort(err);
      throw err;
    });
    this.tasks.push(task);
    return task as Promise<T>;
  }

  async [Symbol.asyncDispose]() {
    this.controller.abort();
    await Promise.allSettled(this.tasks);
  }
}

Usage pattern:

async function loadDashboard(userId: string, parentSignal: AbortSignal) {
  const scopeSignal = AbortSignal.any([
    parentSignal,
    AbortSignal.timeout(8000),
  ]);
  const scopeController = new AbortController();
  const combinedSignal = AbortSignal.any([scopeSignal, scopeController.signal]);

  await using scope = new TaskScope();

  const [user, settings, notifications] = await Promise.all([
    scope.spawn((sig) => fetchUser(userId, sig)),
    scope.spawn((sig) => fetchSettings(userId, sig)),
    scope.spawn((sig) => fetchNotifications(userId, sig)),
  ]);

  return { user, settings, notifications };
}

When any spawned task fails, the catch handler triggers this.controller.abort(), propagating cancellation to all siblings. The asyncDispose method ensures all tasks settle before the scope releases.

AsyncLocalStorage as Context Carrier

For server environments, AsyncLocalStorage (Node.js 24+ with AsyncContextFrame backend) carries cancellation tokens and request metadata across async boundaries without explicit parameter threading:

import { AsyncLocalStorage } from 'node:async_context'; // Node 24+

const requestContext = new AsyncLocalStorage<{ signal: AbortSignal; requestId: string }>();

app.use((req, res, next) => {
  const controller = new AbortController();
  res.on('close', () => controller.abort(new Error('client disconnected')));
  requestContext.run({ signal: controller.signal, requestId: req.id }, next);
});

async function anywhereInTheStack() {
  const { signal, requestId } = requestContext.getStore()!;
  // signal propagates cancellation automatically
}

Architecture Decision: The scope provides structure; developers must explicitly thread signals through every cancellable operation. Fetch APIs accept signals natively. Database drivers vary; unsupported drivers require Promise.race wrappers with explicit connection release in the losing branch.

Pitfall Guide

1. Orphaned Task Accumulation: Promise.all rejection does not cancel pending promises. Without explicit disposal or abort propagation, tasks continue holding resources until natural completion, causing pool exhaustion under load.
2. Signal Threading Neglect: TaskScope only provides the cancellation boundary. Every spawned function must actively check and respect the AbortSignal. Forgetting to pass the signal to fetch, DB queries, or timers breaks the cancellation chain.
3. Browser Compatibility Gaps: Safari lacks native await using support as of early 2026. Relying on native runtime behavior in Safari-heavy environments requires TypeScript transpilation or explicit polyfills. Always validate target environment support.
4. Premature Process Termination: Calling process.exit() during async setup bypasses the event loop, preventing await using blocks and cleanup handlers from executing. Use graceful shutdown patterns that await pending disposal before termination.
5. Ignoring LIFO Disposal Order: Multiple await using declarations dispose in reverse registration order. Misordering dependencies (e.g., disposing a connection pool before individual connections) causes runtime errors during cleanup.
6. Driver-Level Cancellation Blind Spots: Not all database drivers natively support AbortSignal. Wrapping queries in Promise.race against the abort signal is mandatory for unsupported drivers, but developers often forget to explicitly release the connection in the race's losing branch, causing silent pool leaks.

Deliverables

• Blueprint: ES2026 Async Lifetime Management Blueprint – Architecture diagram showing signal propagation paths, disposal boundaries, and context carrier integration for Node.js and browser environments.
• Checklist: Async Resource Leak Prevention Checklist – 12-point validation covering signal threading, disposal guarantees, driver compatibility, browser support matrices, and graceful shutdown verification.
• Configuration Templates:
  • TaskScope production-ready configuration with timeout composition and error routing
  • AbortSignal aggregation template for request-scoped, user-interaction, and global shutdown signals
  • AsyncLocalStorage middleware setup for Express/Fastify with automatic client-disconnect abort propagation