`next dev` and `next build` crashing in `next@>=14.2.1-canary.4` on Linux #64468

steve-marmalade · 2024-04-14T15:53:12Z

Link to the code that reproduces this issue

https://github.com/marmalade-labs/canary-crash

To Reproduce

Run any of the following (possibly only affects Linux):

pnpm dev
pnpm run build
Deploy to Vercel

Current vs. Expected behavior

pnpm dev

➜  canary-crash git:(main) pnpm dev

> [email protected] dev /home/stevie/code/canary-crash
> next dev

  ▲ Next.js 14.2.1-canary.4
  - Local:        http://localhost:3000

 ✓ Starting...
➜  canary-crash git:(main) 
➜  canary-crash git:(main) echo $?
0
➜  canary-crash git:(main)

pnpm build

➜  canary-crash git:(main) pnpm run build -d

> [email protected] build /home/steve/code/canary-crash
> next build "-d"

  ▲ Next.js 14.2.1-canary.4

   Creating an optimized production build ...
➜  canary-crash git:(main) 
➜  canary-crash git:(main) echo $?
0

Deploy to Vercel (with Node v 18)

  ▲ Next.js 14.2.1-canary.4
   Creating an optimized production build ...
 ⚠ Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /vercel/path0/node_modules/.pnpm/@[email protected]/node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node: ELF load command past end of file
 ⚠ Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
 ⨯ Failed to load SWC binary for linux/x64, see more info here: https://nextjs.org/docs/messages/failed-loading-swc
> Build error occurred
Error: Jest worker encountered 1 child process exceptions, exceeding retry limit
    at ChildProcessWorker.initialize (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/jest-worker/index.js:1:11580)
    at ChildProcessWorker._onExit (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/jest-worker/index.js:1:12545)
    at ChildProcess.emit (node:events:529:35)
    at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
  type: 'WorkerError'
}
 ELIFECYCLE  Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu, 11 Apr 2024 01:47:33 +0000
  Available memory (MB): 31886
  Available CPU cores: 8
Binaries:
  Node: 18.18.2
  npm: 10.5.2
  Yarn: 1.22.22
  pnpm: 8.15.5
Relevant Packages:
  next: 14.2.1-canary.4 // Latest available version is detected (14.2.1-canary.4).
  eslint-config-next: 14.2.1-canary.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure, App Router, Operating System (Windows, MacOS, Linux)

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), Vercel (Deployed)

Additional context

This may be a Linux-only issue, since @ztanner was not able to reproduce, per #64432 (comment)

One possible clue is that https://www.npmjs.com/package/@next/swc-linux-x64-gnu/v/14.2.1-canary.4 has an unpacked size of 88.2 MB whereas https://www.npmjs.com/package/@next/swc-linux-x64-gnu/v/14.2.1-canary.3 has an unpacked size of 131 MB. So maybe there was an issue generating this linux build artifact in the latest canary?

The text was updated successfully, but these errors were encountered:

vordgi · 2024-04-14T16:12:54Z

Same thing. Ubuntu (Github workflow):

On Windows it works with no problems

steve-marmalade · 2024-04-15T01:12:42Z

Confirmed that this is still an issue in 14.2.1-canary.5.

FWIW https://www.npmjs.com/package/@next/swc-linux-x64-gnu/v/14.2.1-canary.5 is also 88MB, so that theory still stands (although it now seems unlikely it was due to a flaky build).

mwskwong · 2024-04-15T02:29:33Z

Same thing. Ubuntu (Github workflow):

On Windows it works with no problems

I tried it on both Windows and Mac and it works normally when I build the same project on both OS, but as soon as I deploy to Vercel, which is using Linux, I either get a pretty generic error:

Error: No serverless pages were built

Or sometimes a more specific one:

 ⚠ Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /vercel/path0/node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node: ELF load command past end of file
 ⚠ Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
 ⨯ Failed to load SWC binary for linux/x64, see more info here: https://nextjs.org/docs/messages/failed-loading-swc
> Build error occurred
Error: Jest worker encountered 1 child process exceptions, exceeding retry limit
    at ChildProcessWorker.initialize (/vercel/path0/node_modules/next/dist/compiled/jest-worker/index.js:1:11580)
    at ChildProcessWorker._onExit (/vercel/path0/node_modules/next/dist/compiled/jest-worker/index.js:1:12545)
    at ChildProcess.emit (node:events:529:35)
    at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
  type: 'WorkerError'
}
Error: Command "npm run build" exited with 1

It is not reproducible as soon as I roll back to 14.2.1-canary.3. So perhaps the binary of SWC for Linux is missing from the build?

franky47 · 2024-04-15T02:42:29Z

Same issue in nuqs, next build started failing with 14.2.1-canary.4, and still does with 14.2.1-canary.5. 14.2.1-canary.3 passes fine.

The worst part of this is that Turborepo caches the failed output (because of the exit code 0), so retries will use the failed cache.

typeofweb · 2024-04-15T05:14:45Z

Same issue on Vercel:
Error: Command "pnpm run build" exited with SIGBUS

faresharmali · 2024-04-15T07:07:20Z

Having the same issue with vercel (i'm still on next version 12.2.1)

### What? There is a race condition in the `pull-build-cache` script. When the remote cache entry was removed between the dry run and the real run, it will run the command and caches whatever is in the native folder. Seems like there are some very old leftover files there which lead to an broken publish. This changes the command to fail when there are no files and empties the folder before running the script. This should lead to pull-build-cache to failing instead. Closes PACK-2957 Fixes #64468

timneutkens · 2024-04-15T10:44:12Z

Landed #64493 and triggered a new canary release. Will monitor when it's published.

franky47 · 2024-04-15T11:29:20Z

@timneutkens I can confirm 14.2.1-canary.6 fixed the build issue, thanks!

https://github.com/47ng/nuqs/actions/runs/8688135747

steve-marmalade · 2024-04-15T16:01:39Z

Awesome, thanks @timneutkens

Thinkscape · 2024-04-17T00:30:27Z

Confirming 14.2.1-canary.5 was crashing, 14.2.1-canary.6 builds on Vercel a-ok 👍

### What? There is a race condition in the `pull-build-cache` script. When the remote cache entry was removed between the dry run and the real run, it will run the command and caches whatever is in the native folder. Seems like there are some very old leftover files there which lead to an broken publish. This changes the command to fail when there are no files and empties the folder before running the script. This should lead to pull-build-cache to failing instead. Closes PACK-2957 Fixes #64468

github-actions · 2024-05-01T12:02:01Z

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

steve-marmalade added the bug Issue was opened via the bug report template. label Apr 14, 2024

github-actions bot added the area: OS label Apr 14, 2024

steve-marmalade mentioned this issue Apr 14, 2024

Parallel / Intercepting Route (Modal) won't close until Server Action completes #64432

Closed

vordgi mentioned this issue Apr 14, 2024

Fix test workflows vordgi/nimpl-getters#49

Closed

steve-marmalade changed the title ~~next dev and next build crashing in v14.2.1-canary.4 on Linux~~ next dev and next build crashing in next@>=14.2.1-canary.4 on Linux Apr 15, 2024

Marukome0743 mentioned this issue Apr 15, 2024

✨feat: implement image preview OpenUp-LabTakizawa/dcrs#354

Merged

3 tasks

timneutkens mentioned this issue Apr 15, 2024

improve turborepo caching #64493

Merged

timneutkens closed this as completed in #64493 Apr 15, 2024

github-actions bot added the locked label May 1, 2024

github-actions bot locked as resolved and limited conversation to collaborators May 1, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`next dev` and `next build` crashing in `next@>=14.2.1-canary.4` on Linux #64468

`next dev` and `next build` crashing in `next@>=14.2.1-canary.4` on Linux #64468

steve-marmalade commented Apr 14, 2024 •

edited

Loading

vordgi commented Apr 14, 2024

steve-marmalade commented Apr 15, 2024

mwskwong commented Apr 15, 2024 •

edited

Loading

franky47 commented Apr 15, 2024 •

edited

Loading

typeofweb commented Apr 15, 2024

faresharmali commented Apr 15, 2024 •

edited

Loading

timneutkens commented Apr 15, 2024

franky47 commented Apr 15, 2024 •

edited

Loading

steve-marmalade commented Apr 15, 2024

Thinkscape commented Apr 17, 2024

github-actions bot commented May 1, 2024

next dev and next build crashing in next@>=14.2.1-canary.4 on Linux #64468

next dev and next build crashing in next@>=14.2.1-canary.4 on Linux #64468

Comments

steve-marmalade commented Apr 14, 2024 • edited Loading

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

pnpm dev

pnpm build

Deploy to Vercel (with Node v 18)

Provide environment information

Which area(s) are affected? (Select all that apply)

Which stage(s) are affected? (Select all that apply)

Additional context

vordgi commented Apr 14, 2024

steve-marmalade commented Apr 15, 2024

mwskwong commented Apr 15, 2024 • edited Loading

franky47 commented Apr 15, 2024 • edited Loading

typeofweb commented Apr 15, 2024

faresharmali commented Apr 15, 2024 • edited Loading

timneutkens commented Apr 15, 2024

franky47 commented Apr 15, 2024 • edited Loading

steve-marmalade commented Apr 15, 2024

Thinkscape commented Apr 17, 2024

github-actions bot commented May 1, 2024

`next dev` and `next build` crashing in `next@>=14.2.1-canary.4` on Linux #64468

`next dev` and `next build` crashing in `next@>=14.2.1-canary.4` on Linux #64468

steve-marmalade commented Apr 14, 2024 •

edited

Loading

mwskwong commented Apr 15, 2024 •

edited

Loading

franky47 commented Apr 15, 2024 •

edited

Loading

faresharmali commented Apr 15, 2024 •

edited

Loading

franky47 commented Apr 15, 2024 •

edited

Loading