[M2] Command failed with signal "SIGABRT" when starting gatsby develop

[n0hack]

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

The first time i start a project, it starts right. However, when restarting afterwards, error Command failed with signal "SIGABRT" occurs. Since there is no problem afte the gatsby clean command on a similar issue, i made the command "yarn clean && yarn develop" and using this command. But it's uncomfortable to use every start.

Reproduction Link

https://github.com/n0hack/TIL/tree/main/%EA%B3%B5%EC%8B%9D%20%EB%AC%B8%EC%84%9C/frontend/gatsby

Steps to Reproduce

$ yarn develop
<<< Press ctrl + c to exit
$ yarn develop
<<< Error occurred

Expected Result

expected it to start right

Actual Result

yarn run v1.22.19
$ gatsby develop
⠋ compile gatsby files
node(58544,0x170d07000) malloc: Incorrect checksum for freed object 0x13cf632f8: probably modified after being freed.
Corrupt value: 0xa36b6147da7dfeba
node(58544,0x170d07000) malloc: *** set a breakpoint in malloc_error_break to debug
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Environment

System:
    OS: macOS 13.6
    CPU: (8) arm64 Apple M2
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.0 - /opt/homebrew/opt/nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.8.1 - /opt/homebrew/opt/nvm/versions/node/v18.18.0/bin/npm
  Languages:
    Python: 3.11.5 - /Users/lucid/.pyenv/shims/python
  Browsers:
    Chrome: 117.0.5938.92
    Safari: 16.6
  npmPackages:
    gatsby: ^5.12.4 => 5.12.4
    gatsby-plugin-image: ^3.12.0 => 3.12.0
    gatsby-plugin-sass: ^6.12.0 => 6.12.0
    gatsby-plugin-sharp: ^5.12.0 => 5.12.0
    gatsby-source-filesystem: ^5.12.0 => 5.12.0

Config Flags

No response

[n0hack]

same error occured after using "yarn build"

[schettn]

Might be related: #38483 (comment)

---

Hmmm, you know, I've been wondering, what's the deal with the Gatsby team and these issues? Does anyone know why the Gatsby team doesn't seem to react to them anymore? I mean, seriously, I've been checking out the recent stuff from the past month, and guess what? None of them seem to have shaken off their "status: triage needed" labels.

@LekoArts ?

[LekoArts]

See #38483 (comment)