absolute mem

absolute mem lists every running AbsoluteJS server by resident memory (RSS), biggest first, alongside your system's total usage. It reads RSS externally — no server changes needed — so it works on dev, start, compiled, and untracked servers alike. Add --json for the per-server and system numbers in a scriptable shape (handy for CI memory budgets).

# Memory report for every running server, biggest first
absolute mem

# Diff two heap snapshots by object type to find leaks
absolute mem diff before.heapsnapshot after.heapsnapshot

# Machine-readable (per-server RSS + system totals)
absolute mem --json

Each row is a server with its RSS and a bar showing its share of total system memory, followed by the resident total and the system's used/free split. One caveat specific to Bun: RSS often stays high because the allocator doesn't return freed memory to the OS, so a big RSS isn't necessarily a leak — it's the fast, at-a-glance view. For the real leak signal, take a heap snapshot.

$ absolute mem
  NAME     SOURCE     PORT  RSS       % SYS
  my-app   dev        3000  142.6 MB  ███░░░░░░░░░░ 0.9%
  api      untracked  3001  88.1 MB   ██░░░░░░░░░░░ 0.5%

  2 servers · 230.7 MB resident total
  system  6.2 GB / 16.0 GB used · 9.8 GB free

While absolute dev is running, press m (or type heap) to dump a heap snapshot of the server to your project root. It's a standard V8 .heapsnapshot you can load in Chrome DevTools under Memory — where heapUsed growing across snapshots is the reliable sign of a real leak, unlike RSS. Take two snapshots and run absolute mem diff a.heapsnapshot b.heapsnapshot to see exactly which object types grew between them — the leak, named. Also wired up: absolute ps --watch shows a live memory peak and trend sparkline per server.

$ absolute dev
  ...
# press  m  (or type: heap)
[absolute] heap snapshot written: heap-48210-1716600000000.heapsnapshot
# load it in Chrome DevTools › Memory › Load