Command failed with signal "SIGSEGV" & segmentation fault

[yesh]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

After updating all gatsby packages to the latest 5.3.0 version, yarn dev and yarn build both throw the error:

error Command failed with signal "SIGSEGV".

gatsby develop and gatsby build both throw the error:

[1] 12714 segmentation fault gatsby develop
[1] 12739 segmentation fault gatsby build

with the 5.2.0 version everything worked flawlessly.
I also tried deleting and rebuilding the node_modules folder with no success.

Reproduction link

Suggested reproduction services are not working because of Node 18 requirement.
The issue can be hardware related for m1 / arm architecture cpus.

Steps to Reproduce

• npx gatsby new errortest
• cd errortest
• npm upgrade
• gatsby develop

Expected Result

running or building

Actual Result

Environment

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1 Pro
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Edge: 102.0.1245.44
    Firefox: 107.0.1
    Safari: 16.1
  npmPackages:
    gatsby: ^5.2.0 => 5.3.0 
    gatsby-plugin-image: ^3.2.0 => 3.3.0 
    gatsby-plugin-postcss: ^6.2.0 => 6.3.0 
    gatsby-plugin-react-helmet: ^6.2.0 => 6.3.0 
    gatsby-plugin-robots-txt: ^1.8.0 => 1.8.0 
    gatsby-plugin-sharp: ^5.2.0 => 5.3.0 
    gatsby-plugin-sitemap: ^6.2.0 => 6.3.0 
    gatsby-source-contentful: ^8.2.0 => 8.3.0 
    gatsby-source-filesystem: ^5.2.0 => 5.3.0 
    gatsby-transformer-sharp: ^5.2.0 => 5.3.0 
  npmGlobalPackages:
    gatsby-cli: 5.3.0

Config Flags

No response

[LekoArts]

Hi!

Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it.

If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look.

Thanks for using Gatsby! 💜

[denisgoryaynov]

I am also having the same issue after upgrading to 5.3.0, I tried creating a new project using the default starter and then updating the versions to 5.3.0 and the problem still happens:
npx gatsby new test https://github.com/gatsbyjs/gatsby-starter-default

This is my system information:

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn
    npm: 9.2.0 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Safari: 16.1
  npmPackages:
    gatsby: ^5.3.0 => 5.3.0
    gatsby-plugin-image: ^3.3.0 => 3.3.0
    gatsby-plugin-manifest: ^5.3.0 => 5.3.0
    gatsby-plugin-sharp: ^5.3.0 => 5.3.0
    gatsby-source-filesystem: ^5.3.0 => 5.3.0
    gatsby-transformer-sharp: ^5.3.0 => 5.3.0

[OPITOs]

npx gatsby new test https://github.com/gatsbyjs/gatsby-starter-default
and updating to 5.3.0

on Windows

We encountered an error while trying to load your site's gatsby-config. Please fix the error and try again.
Error: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

[yesh]

Hi!

Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a minimal reproduction. This is a simplified example of the issue that makes it clear and obvious what the issue is and how we can begin to debug it.

If you're up for it, we'd very much appreciate if you could provide a minimal reproduction and we'll be able to take another look.

Thanks for using Gatsby! 💜

I don't think a reproduction is necessary or useful, from checking around is possible the issue is related to apple m1 / arm architecture.
anyway you can test it with:

• npx gatsby new errortest
• cd errortest
• npm upgrade
• gatsby develop

[LekoArts]

Sorry for the inconveniences this is causing, we'll look into it today and rollout a fix. About the Windows issue, please go to #37251

Sidenote: Please don’t comment „+1“, GitHub has an emoji reaction system

[LekoArts]

We're pretty sure that the lmdb upgrade is the cause and have prepared a PR to revert that commit: #37255

Also it seems to only happen on Mac, we couldn't reproduce on WSL or Windows.

Once merged we'll test that it resolves it (on all platforms) and then backport as 5.3.1

[LekoArts]

I opened kriszyp/lmdb-js#206 to hopefully get to the bottom of this 👍 The revert PR is merged and in our testing it works again, so we'll release 5.3.1 shortly.

[LekoArts]

Fixed in gatsby@5.3.1 🎉