Next-build: intercept failure of a worker thread and exit with status 1 #67154
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
If process run out of heap memory during next.js build process, it exits with error code 0, resulting in a "silent failure".
Why?
Looks like the build tasks are delegated to workers instantiated inside
packages/next/src/build/webpack-build/index.ts
How?
Intercept failure of a worker and exit with code 1
Closes NEXT-
Fixes #67097