9 people reported

All time, since Oct 12, including 8 thumbs-up on GitHub.

Build spawns a webpack-loader pool per loader chain and context

“Any count above 2 therefore means more than one pool.”

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/11842/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

Since 16.4.0-canary.39, next build with Turbopack creates hundreds of Node.js processes, leading to OOM.

Is this your bug?

Where: Turbopack build
Versions: 16.4.0
Platforms: macOS
How bad: Stops work: a core feature can't be used.

Not quite your bug?

Slow Turbopack production build1 person
Loaders get stale file content2 people
Build hangs on worker import cycle3 people

Original reports1, newest first

Oct 12, 2026Turbopack: next build spawns one webpack-loader process pool per loader chain × context since 16.4.0-canary.39 (hundreds of Node.js processes, OOM)On GitHub#100064

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.