1 person reported
All time, since Aug 25.
Turbopack dev server livelocks
“No Compiling / line, no error, no timeout — the server never serves a single request.”
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/next-js/issues/4361/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
Turbopack dev server livelocks and never serves requests. On macOS Apple Silicon pnpm workspaces, next-server spins at 603–777% CPU after "Ready" while requests hang.
Is this your bug?
File my report- Where
- Turbopack dev server
- Versions
- 16.4.0-canary.6
- Platforms
- macOS
- How bad
- Stops work: a core feature can't be used. Most reports say it used to work. Some reports say it blocks them completely.
Not quite your bug?
Original reports3, newest first
- Turbopack dev livelocks on darwin-arm64 (pnpm workspace): 603% CPU, never serves a request — unfixed on every stable through 16.3.2, fixed in canary by #96808On GitHub#97850
- Turbopack dev livelocks on darwin-arm64 (pnpm workspace): 603% CPU, never serves a request — unfixed on every stable through 16.3.2, fixed in canary by #96808On GitHub#97849
- Turbopack dev livelocks on darwin-arm64 (pnpm workspace): 603% CPU, never serves a request — still unfixed on every stable through 16.3.2, fixed in canary by #96808On GitHub#97847