Turbopack Error: Failed to write app endpoint /page, Happened after reloading Cursor

[dawood8080]

Turbopack version: 23c46498
Next.js version: 0.0.0

Error message:

Turbopack Error: Failed to write app endpoint /page

This error appears after multiple reloads of the Cursor. I asked GLM-5.1, and he answered me the following:

Root cause: Windows error 1450 — "Insufficient system resources." The repeated Cursor reloads caused Turbopack's cache (RocksDB) to balloon with thousands of .sst/.meta files, exhausting Windows file handle/memory limits. The "random numbers typing" was the cache spiraling out of control.
Fixed: I killed the lingering Node processes and deleted the corrupted .next cache.
Next step: Run npm run dev again — it should work now with a fresh cache.

And now it works fine. I hope this can help someone

[akshay-kumar-singh]

I was able to reproduce similar behavior on Windows after repeated hot reloads/restarts during development.

This looks related to Turbopack cache growth and Windows filesystem/resource limits rather than the app code itself.

Things that helped in my case:

1. Kill lingering Node.js processes

taskkill /F /IM node.exe

2. Remove .next cache completely

rmdir /s /q .next

3. Reinstall dependencies if needed

rm -rf node_modules package-lock.json
npm install

4. Restart dev server

npm run dev

Possible cause:
Repeated reloads/restarts (especially with Cursor + Turbopack + Windows) may leave stale cache handles or rapidly grow RocksDB cache files (.sst, .meta), eventually triggering Windows resource exhaustion errors.

Might be worth checking:

• cache cleanup behavior
• lingering file handles
• Windows-specific junction/file lock handling
• Turbopack cache invalidation during repeated editor reloads