#How to resolve segmentation fault?
1 messages · Page 1 of 1 (latest)
🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord
🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize
✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)
What shell did u run this in? Vscode's terminal?
yes, and even tried with git bash as well.
Could u try in vscodes terminal again or in a command prompt window? Not in git bash
And send the output
fails silently with no error
Whats ur nodejs version? Also did you run npm install ahead of time?
tried with different nodejs versions. 20, 22, 24
created this proj with npx so npm install was not needed
ah right
weird tho. im on 24 rn with no issues. what if u try to run npm build and then node .next/standalone/server.js (i think thats the right path)
wait no thats for standalone
hang on
hm nevermind that only exists for standalone builds sorry. did u change any default configuration options for create-next-app? if not im not sure i can help any further
no, i didn't change anything
it works with next.js earlier version btw
I tried with v14.2.33 and it works
mby just try to delete n run npx again but make sure ur in a command prompt not git terminal
u tried a separate npx create-next-app? or just changed the version using npm?
yes i tried seperate npx create next app
ah it fails again 😭
https://github.com/vercel/next.js/discussions/43436
I found this but its not answered yet. segmentation fault is difficult to debug
try adding --webpack in args, it could be smth in turbopack
You mean by npm run dev --webpack ?
yeah
yeah tried with that but not working too
damn, so your cmd/git bash and another person ages ago on macos had it too
very weird
out of curiosity, i kinda want to see if https://bun.com runtime gives a better stack trace for crash lol (but its fine if thats too much changes for you)
# install bun on windows
powershell -c "irm bun.sh/install.ps1 | iex"
# init a new one just in case, but it should still work decently with npm's install
bunx --bun create-next-app
# run next dev in bun runtime
bun --bun run dev
oh also you arent on windows arm are you?
you prob would know if you were using it, but some low-end new laptops run on windows arm and it has really native apps bad support, so nearly everything is emulated (which creates cases for easy crashes)
yes im using it and its not arm, it's intel based
cool cool
and its not like a really old one is it
-# (if it were, bun would refuse to install i believe anyway lol)
its considerably good one 😁
yooo
OMG, what did I do wrong? Im innocent, even bun fails on my end
whats the terminal output if you dont mind