[NEXT-939] SIGSEGV on `next build` with 13.2.4

[aplr]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.13.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: 7.26.0
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected?

next build CLI

To Reproduce

I'll dig into it, maybe I can reproduce it easily. However I'd expect next build not to segfault on my existing codebase which works on 13.2.3 without changes other than upgrading next.

Describe the Bug

After upgrading next to 13.2.4, when running next build, I'm running into a segfault.

As you can see, I'm using the app dir (only). Tell me if you need more info.

$ next build --experimental-app-only
info  - Loaded env from /next/apps/web/.env.local
info  - Loaded env from /next/apps/web/.env.production
warn  - You have enabled experimental features (appDir, swcPlugins, serverComponentsExternalPackages) in next.config.mjs.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback

(node:83878) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Command: /user/.nvm/versions/node/v18.13.0/bin/node
Arguments: /user/.cache/node/corepack/yarn/1.22.19/lib/cli.js build
Directory: /next
Output:

info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.

Expected Behavior

No Segfault when running yarn build

How are you deploying your application? (if relevant)

On Vercel, where it's also segfaulting. (Also in my Docker build)

_NEXT-939

[aplr]

Ok I've found the troublemaker, it's the SWC plugin @graphql-codegen/client-preset-swc-plugin. I've created an issue there: dotansimha/graphql-code-generator#9145.

It's only happening since next 13.2.4, were there any dependency updates / changes which could cause this issue?

Also, is there a way to tell where to look for such issues, i.e. better error messages so one finds the underlying cause faster?

[jinojacob15]

Same issue with me , After updating to 13.2.4 ,dev is working fine but yarn build and yarn start (prod build) gives me error

[jinojacob15]

@aplr is @graphql-codegen/client-preset-swc-plugin in built with apollo client ??. I am not using @graphql-codegen/client-preset-swc-plugin in my code i checked.

[SuttonJack]

Getting the same error. It was introduced for me at next@13.2.4-canary.6

Version next@13.2.4-canary.5 and below all work fine

[SuttonJack]

@shuding Could this stem from #46881 ? These ChunkLoadError messages in the console seem to be coming from react rather than next

One other note - this only occurs on deployment or after running next build && next start

next dev works fine

[aplr]

I'm not sure if the issues I and you reported in this ticket are related in any way, as I get segfaults at build-time caused by a swc plugin

[martinnabhan]

I can confirm I get the same error when using next-superjson-plugin (which is a SWC plugin). If I remove the plugin from next.config.js building works again. I'll look into this some more. SWC seems to be the common link.

Edit: After testing different Next.js versions, the error seems to be introduced by 13.2.4-canary.9. I can also confirm I'm getting the same error on 13.2.5-canary.1.

Edit 2: I can confirm that in my case reverting #46971 and rebuilding @next/swc fixed the error for me.

[icyJoseph]

Hi,

Do you guys have 32 bits architecture? or if you run node -p "process.arch", does it match your OS?

[Timothee-P]

@jinojacob15 and @SuttonJack:
The same errors occur in my project after updating next to 13.2.4. It doesn't seems related to this issue and SWC, but more to dynamic imports.
Just to let you know I have created a new issue #47173

[jinojacob15]

@Timothee-P @SuttonJack @aplr I Spent two days in debugging the issue , finally code was working when i removed dynamic imports with ssr:false .
But there was a bizarre issue that even when i downgraded the next version to 13.2.3 and still issue persisted .