Segmentation fault while adding dynamic routes in next js
deployment ID: 3a2e0d9f-f159-49c3-a519-8e4d582e08e8
account ID: d5b5751efdc386eae183fed7730f526f
Hi, I am trying to deploy my next.js app on pages. But it shows Segmentation fault when trying to deploy with multiple paths under a dynamic route.
This error goes away if I keep maximum of 1 path under dynamic route.
The project build perfectly on my local machine.
4 Replies
Hi @codename_404 🙂 👋
I just checked the logs... it just looks like the Vercel build process generates the segmentation fault...
nothing looks clearly wrong with the Pages build system....
just to be sure, do you build the project locally using
next-on-pages?
also, is there any chance you could share your code or a minimal reproduction showcasing the error?Hi @dario_p ~
After a lot of extensive tests, I found something very unusual.
Some client components are causing this Fault when i add icons from react-icons package.
This is the only thing that is causing this issue. Not even all the files are causing this issue. From what I found, client comps which are rendering from a server comp that is using the edge endpoint is causing this issue, might have some other reasons but this is what i found so far.
@codename_404 have you made any progress with this? 🙂
Yes. I have made a system outside of that project, to convert SVGs to Pngs.
The problem happens with svgs any kind of svg not all the time however specially in client components that renders from server component.
So I made my own icon system with pngs to change colors sizes etc. And everything works fine.
Thank you bother, for checking back ~