next/image on node 16 give SIGSEGV

[artecoop]

What version of Next.js are you using?

10.1.3

What version of Node.js are you using?

16.0.0

What browser are you using?

Chrome, Firefox

What operating system are you using?

macOS 11.2.3

How are you deploying your application?

next dev

Describe the Bug

Mac Mini M1, Node 16 next start crashes hitting next/images
Already nuked node_modules and locks after updating node version

$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Loaded env from /Users/vfornito/DEV/gvdp/vdp/.env.development
info  - Using webpack 4. Reason: future.webpack5 option not enabled https://nextjs.org/docs/messages/webpack5
(node:2822) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /Users/vfornito/DEV/gvdp/node_modules/next/node_modules/postcss/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
event - compiled successfully
event - build page: /
wait  - compiling...
event - compiled successfully
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Expected Behavior

To work :)

To Reproduce

Use a simple next/image on a next.js project. Either using js or TS does not change the behavior

[apollonian]

Could something else be the cause of this? (M1?) Image works fine for me on node v16.0.0 (Intel/macOS)!

[artecoop]

Node V16 introduced the support for Apple silicon, could be this the cause?

I'm experiencing this problem too. Just tested in a fresh installed macOS and a simple Next JS project. It crashes using either Node LTS or 16.0.0. My dev script works fine until you scroll into view any next/image component, so maybe the bug its related with the lazy loading?

I can confirm it only happens in my dev environment, pushing to production works completely fine for me. I'm using a MacBook Air M1 and deploying to Vercel, if that helps.

[lavgup]

Updated to Node v16 via Homebrew on my M1 Mac Mini and faced the same issue. Was able to start up the dev environment but going to a page with next/image crashed the server. Downgrading to Node v15.14.0 fixed the issue (plus got rid of many warnings due to lack of support for v16).

[RuiGuilherme]

Postcss has issue about this and lasted version of postcss fix this issue.

You can try go to node_modules/next and run yarn add postcss. But I think this can break NextJS.

[16abhimasani]

Also seeing this error (crashes application); fresh install of node on M1 goes to v16. Adding postcss latest version manually to top level does not fix issue.

[16abhimasani]

when can we expect this bug fix to be released (seeing next @ 10.1.3 still)? just saw that you merged in the change

[16abhimasani]

Just upgraded to next@10.2.0 and actually still getting SIGSEGV error when next/image is on page. @artecoop can you confirm that this is either working or fixed for you? I am curious if I need to downgrade from node v16

I'm still getting it, although less often. Using Node v16 with next@10.2.0 and postcss@8.2.13. I don't know what I'm doing wrong but I get the same problem with Node LTS. Tried using nvm use --lts