WhatBrokeToday
GTA 6FAQ
Bun

Bun Child Process stdout and process.stdin Stop Emitting Events on Stream State Transitions

high

Is it fixed? Not yet.

Ongoing since Nov 10, 20:43 UTC. First reported Nov 10, 20:43 UTC.

What happened

Bun child_process stdout stops emitting 'readable' events when stream.read(n) exactly drains the buffer, and process.stdin stops reading entirely when switching from a 'data' to a 'readable' listener inside a 'data' handler. This affects Bun version 1.4.4+38afee6c8 on macOS.

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.

Official fix

Timeline

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

    Child process stdout stops emitting "readable" when read(n) drains the buffer exactly

    Source

Evidence

2 reports · 2 GitHubShow
  1. [1]
    GitHub First report
    Child process stdout stops emitting "readable" when read(n) drains the buffer exactly(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4+38afee6c8 What platform is your computer? Darwin 23.6.0 arm64 arm What steps can reproduce the bug? Summary When a "readable" handler on a child_process stdout stream reads exactly the buffered amount with stream.read(n) (so read() never returns null), Bun often stops emitting "readable". The child keeps writing, Bun keeps buffering (up to the high water mark, 131072 bytes), but no further "readable" event fires, so the reader waits forever. Node.js never…

    by farshed 0upvotes 1comments

  2. [2]
    GitHub
    process.stdin stops reading after switching from 'data' to 'readable' inside a 'data' handler(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4+38afee6c8. The same code is on main. What platform is your computer? Darwin 25.6.0 arm64, macOS 26.7.3 What steps can reproduce the bug? If a 'data' handler on process.stdin calls pause(), removes itself and adds a 'readable' listener in the same tick, Bun stops reading stdin for good. This happens on a TTY and on a pipe. // repro.mjs // bun repro.mjs defer does the switch in setImmediate, and then it works. const defer = process.argv[2] === "defer"; if…

    by itsAster0 0upvotes 1comments93% match

FAQ

What happened in the Bun issue?

Bun child_process stdout stops emitting 'readable' events when stream.read(n) exactly drains the buffer, and process.stdin stops reading entirely when switching from a 'data' to a 'readable' listener inside a 'data' handler. This affects Bun version 1.4.4+38afee6c8 on macOS.

What is affected by the Bun issue?

Bun (versions: 1.4.4+38afee6c8).

When did the Bun issue start and end?

It started Nov 10, 20:43 UTC and is still ongoing (8 d 8 h 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 2 reports from 1 independent source.