I just installed Next.js project with the pnpm next@latest --yes and ran pnpm dev got the above error.
Latest Next.js project has bug?
#ELIFECYCLE Command failed with exit code 3221225477.Segmentation fault
woven nimbus
fading heraldBOT
Hi @woven nimbus. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
The errors you're seeing — ELIFECYCLE Command failed with exit code 3221225477 and segmentation faults — are known issues that have been reported in the Next.js GitHub repository, and they are typically environment-dependent rather than a universal bug in Next.js itself.
Here are the relevant known causes based on the knowledge sources:
1. Windows: Dynamic Linking Issue with next-swc.node
Exit code 3221225477 on Windows is associated with a dynamic link issue in the next-swc.node binary. This was reported as being caused by using clang's lld.exe instead of MSVC's link.exe when generating the SWC binary. [Windows next-swc.node issue]
2. Linux: Segfault Due to LD_PRELOAD
On Linux systems (e.g., Ubuntu Unity), a segmentation fault (exit code 139) can occur if shared libraries are injected via LD_PRELOAD (e.g., libgtk3-nocsd.so.0). This causes the build/dev process to crash immediately. [Linux segfault issue]
3. SWC Binary Not Loading
There are also reports of the SWC binary failing to load entirely, which can cause crashes when running pnpm dev. [SWC binary issue]
What You Can Try
- Check your OS and environment — are you on Windows or Linux with any preloaded libraries?
- On Linux, try running
echo $LD_PRELOADto check if any libraries are being injected, and try unsetting it:unset LD_PRELOAD && pnpm dev. - On Windows, this may be a known SWC binary linking issue that requires a fix from the Next.js team.
- Check Node.js version compatibility — ensure you're using a supported Node.js version.