1 person reported
All time, since Aug 20.
Pending reads exit process early
“Only a read awaited after module evaluation has completed (a floating main(), a Commander action, a .then() chain) is affected.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/5534/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Pending async reads exit process early on Windows. A pending Bun.stdin.text() or rejecting Bun.file() read does not keep the event loop alive after module evaluation, exiting 0.
Is this your bug?
File my report- Where
- file and stdin reads
- Versions
- 1.4.0 to 1.4.2
- Platforms
- Windows
- How bad
- Breaks a normal workflow. Most reports say it used to work.
Not quite your bug?
- WriteStream ignores overridden _write1 person
- Parallel test worker hangs2 people
- writeFile leaves stale trailing bytes2 people
Original reports3, newest first
- Windows: pending Bun.stdin.text() no longer keeps the event loop alive after module evaluation (regression in 1.4.0, worked in 1.3.11–1.3.14)#41850
- Windows: pending Bun.stdin.text() no longer keeps the event loop alive after module evaluation (regression in 1.4.0, worked in 1.3.11–1.3.14)#41849
- Windows: a rejecting Bun.file() read does not keep the event loop alive — process exits 0 mid-await with no output (regression in 1.4.0)#39787