Hi @ffernandoh and @benevbright, welcome to the Vercel Community!
I’m sorry you’re facing this issue. Is it resolved now?
if not, have you tried the steps here?
Hi @anshumanb. I’ve tried switching node versions, regenerating the package.lock, and deploying it many times.
Since I first published this problem, App1 (see my original message) it is still getting SIGSEGV errors.
For App2, the only modification I did was changing an await Promise.all to a for loop with await when requesting the DB. I’m aware that using a Promise.all for querying data may not be a best practice if the process triggers many requests at once (even using a connection pool). But in our case, the number of requests it’s exactly the same every time (just 5) and the number of users is just one in the preview environment (where we observed the first errors). So I doubt that this change had any implications regarding the root issue
i been getting the same too and cannot understand the root cause
Next.js: 15.2.0
-
Prisma: 6.4.1
-
Node: 22
actually…. @sucrebucre ‘s solution seems to fix issue on our project. I don’t see any issue last 24 hours.
I was skeptical it would resolve the issue but yeah. All I did was removing package-lock.json and recreated it. (it had bunch of changes obviously)
We are still seeing too, and on any route (rsc, api route etc), we’ll try to upgrade all packages to see if it will resolve
Deleting package-lock.json and running npm install again seems to fix this issue.
It didn’t solve the issue for me.
I deployed my app to a competitor, same build command, and no issues.
I solved the issue by upgrading from React 19-RC to React 19, and now everything works perfectly