Turbopack Error: failed to receive message

[yunandar2004]

Turbopack version: d1bd5b58
Next.js version: 0.0.0

Error message:

failed to receive message

Caused by:
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of PlainIssue::from_issue failed
- Execution of PlainSource::from_source failed
- Execution of <WebpackLoadersProcessedAsset as Asset>::content failed
- Execution of WebpackLoadersProcessedAsset::process failed
- Execution of evaluate_webpack_loader failed
- failed to receive message
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

[pouriya73]

Hi @yunandar2004

This one is a Windows socket reset problem, not a “your page code” problem.

os error 10054 = connection forcibly closed by the remote host.
In plain terms: Turbopack was talking to a worker/process (often the Webpack-loader bridge) and that process crashed or got killed, so Turbopack can’t “receive message” anymore.

1. Restart dev server (kills stuck workers)

# stop the dev server, then run again
npm run dev

2. Hard clear caches

rm -rf .next .turbo node_modules/.cache
npm install
npm run dev

3. Update / switch off canary

Use latest stable Next.js (recommended) or update to a newer canary.

If you need it stable now: run without Turbopack (remove --turbo).

4. Windows Defender / antivirus

Add your project folder to exclusions (this is a real cause of random worker kills on Windows).

[nextjs-bot]

This discussion appears to be a duplicate of #83856.

Please follow the discussion there: #83856

---

This comment was added automatically by discussion consolidation tool. If you believe this is in error, feel free to re-open the discussion.