Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

@steve-marmalade

Description

@steve-marmalade

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue was opened via the bug report template.locked

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions