WhatBrokeToday
GTA 6FAQ
Bun

Bun 1.4.4 JSC Concurrent GC Stalls Causing Unbounded Heap Growth

high

Is it fixed? Not yet.

Ongoing since Nov 19, 18:41 UTC. First reported Nov 19, 18:41 UTC.

What happened

In long-running standalone Bun 1.4.4 processes utilizing Web Workers, JavaScriptCore garbage collection can intermittently stall for 20+ seconds while the event loop continues. During these stalls, heapTotal grows significantly, leading to out-of-memory crashes.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    JSC concurrent GC stalls in SlotVisitor::drainInParallelPassively(MonotonicTime::infinity()) while HeapHelpers sleep, causing unbounded heapTotal growth

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    JSC concurrent GC stalls in SlotVisitor::drainInParallelPassively(MonotonicTime::infinity()) while HeapHelpers sleep, causing unbounded heapTotal growth(opens GitHub issue in a new tab)

    Summary In a long-running standalone Bun 1.4.4 process (TUI + ~25–32 Web Workers, no Bun CPU profiler enabled), JSC garbage collection intermittently stops finishing for 20+ seconds while the JS event loop keeps running normally. During the stall, process.memoryUsage().heapUsed stays byte-identical while heapTotal grows by +2.4 GB in ~20 s (and in an earlier macOS occurrence, from 5.3 GB to 45.4 GB over ~69 s before OOM). Two separate Linux gdb captures taken at the moment of the stall show…

    by pkyIntelligence 0upvotes 1comments

FAQ

What happened in the Bun issue?

In long-running standalone Bun 1.4.4 processes utilizing Web Workers, JavaScriptCore garbage collection can intermittently stall for 20+ seconds while the event loop continues. During these stalls, heapTotal grows significantly, leading to out-of-memory crashes.

What is affected by the Bun issue?

Bun (versions: 1.4.4).

When did the Bun issue start and end?

It started Nov 19, 18:41 UTC and is still ongoing (1 h 42 min so far). This page updates as it develops.

How do I get alerts for Bun?

Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.