Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Partial Prerendering] Error: Runtime exited with error: signal: segmentation fault #63947

Open
juliusmarminge opened this issue Apr 1, 2024 · 1 comment
Labels
bug Issue was opened via the bug report template.

Comments

@juliusmarminge
Copy link
Contributor

Link to the code that reproduces this issue

https://github.com/juliusmarminge/trellix-trpc

To Reproduce

no clue... happens seemingly random in prod, never had it locally

Current vs. Expected behavior

Here is a snapshot from my logs:

CleanShot 2024-04-01 at 21 29 16@2x

This is followed by:

CleanShot 2024-04-01 at 21 32 19@2x

So I have no clue if this is a Next.js bug or a Node.js one, but figured I'd start here since I am using some experimental stuff from Next

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.13.1
Relevant Packages:
  next: 14.2.0-canary.51 // Latest available version is detected (14.2.0-canary.51).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.3
Next.js Config:
  output: N/A

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

Not sure

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

Vercel (Deployed)

Additional context

Sorry for a very unclear issue, but just throwing it out here and seeing if this may be a known issue? I've got the error like 5 times over the last 12 hours

@juliusmarminge juliusmarminge added the bug Issue was opened via the bug report template. label Apr 1, 2024
@juliusmarminge
Copy link
Contributor Author

juliusmarminge commented Apr 3, 2024

Seems like this might ahve been a Node.js issue unrelated to PPR that's fixed in 20.12: nodejs/node#52319. When can we expect Vercel to update the Node version on lambdas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

1 participant