Segmentation fault on NextJS 14/13.5 website

Support
,
1

Hello,

I have an issue with a website freshly updated to NextJS App Router. The website was working perfecty with the Pages Router.
After a successful build, on the main page load, I’m getting this error :

Runtime.ExitError - RequestId: b60addd0-6d7f-42d1-b9f9-3ecca20acc1a Error: Runtime exited with error: signal: segmentation fault

Connection details

Netlify internal ID: 01HFCDTE6ZR320KYSMM01R3Q6V

Currenttly the website is online (lucky deploy) but all prefech requests are failing with the same error.
Note : The website is fully server side generated. And it’s working without issue in local prod mode

Website id : lively-blini-24d764

3

Next.js 14 is known to have several issues, this could likely be one more. You can use next.js 13.3 or 13.4 at the moment.

4

I went down to version 13.5.6, and exact same issue. Then I tried version 13.4.19, it’s a bit different : error 500 from netlify :frowning:

5

13.4.x is the latest version we recommend; later versions will not work well.

Once you’ve downgraded, you should be able to see what is causing the 500 errors in your function logs, have you checked them in our admin UI?

6

I see thanks, looks like I’m in this situation : Server.edge not defined Error on nextJS SSR functions cause site to return 500 Errors … I’ll check what I can do

7

I managed to make It work with some adjustement on data cache params, but prefech routes still throw 500 errors. Not ideal (because there’s no client side routing…), but this will do for now :person_shrugging: