Windows 11 Insomnia 13.2.0 intermittently crashes with EPIPE in logger transport
Author: rahulsuvarnaCreated Sep 21, 2026Updated Sep 21, 2026
LabelsB-bugS-unverified
Expected Behavior
Insomnia should continue running normally and should not display a JavaScript error dialog when logging output is written.
An intermittent logging or stream failure should be handled internally without crashing the Electron main process.
Actual Behavior
Insomnia intermittently displays:
A JavaScript error occurred in the main process
The error reports:
Uncaught Exception:
Error: EPIPE: broken pipe, write
The stack trace includes Node stream functions, console.error , transport.write , _Logger.processMessage , and _Logger.logData .
The issue has also occurred for a colleague using the same Insomnia version and environment.
### Reproduction Steps
```markdown
1. Install and open Insomnia 13.2.0 on Windows 11.
2. Use Insomnia normally, including opening a workspace and sending or editing requests.
3. Leave the application running and repeat normal operations until the issue occurs.
4. Observe the error dialog: "A JavaScript error occurred in the main process".
5. Dismiss the dialog and note that the application may become unstable or terminate.
The issue is intermittent, so the exact action that triggers it is not currently known.
### Is there an existing issue for this?
- [x] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Which sync method do you use?
- [ ] Git sync.
- [x] Insomnia Cloud sync.
- [x] Local only
### Additional Information
- Insomnia: 13.2.0
- Build date: 25/08/2026
- OS: Windows_NT x64 10.0.26200
- Electron: 43.2.0
- Node: 24.18.0
- Node ABI: 148
- V8: 15.0.1240245-electron.0
- Architecture: x64
- Installation method: Windows installer downloaded from the official Insomnia website
### Investigation
The error indicates that Insomnia's logger attempted to write to a pipe or stream after the other end had closed.
This appears related to the stdout EPIPE fix in PR #9984:
https://github.com/Kong/insomnia/pull/9984
However, this report is on Windows and the stack references:
- `transport.write`
- `_Logger.processMessage`
- `_Logger.logData`
Please investigate whether another logger transport, child-process pipe, IPC channel, or Windows-specific stream is missing equivalent EPIPE handling.
The issue affects more than one user in the same environment.
A screenshot of the error dialog is attached.
### Insomnia Version
13.2.0
### What operating system are you using?
Windows
### Operating System Version
Windows 11, build 10.0.26200
### Installation method
Downloaded from insomnia.rest and installed using the Windows installer
### Last Known Working Insomnia version
_No response_Source: Kong/insomnia