✅ - Segmentation fault running sandbox | AWS Amplify | Page 1

elfin solstice Apr 15, 2024, 9:58 AM

#

Weird one - after everything running fine for a few weeks, I've started getting a segfault when trying to run sandbox. Haven't changed/updated anything on my end as far as I know. Any ideas on how to troubleshoot or get a stack trace etc.?

`~ npx amplify sandbox
Amplify Sandbox

Identifier: <xxx>
Stack: amplify-reactamplifygen2-<xxxx>

To specify a different sandbox identifier, use --identifier
[1] 3100 segmentation fault npx amplify sandbox`

elfin solstice Apr 15, 2024, 12:39 PM

#

Some more information:

Happens on a completely clean/new projects
Happens with node 20 or 21, fine on node 18

rigid fulcrum Apr 15, 2024, 4:24 PM

#

Hi @elfin solstice , can you create a github issue on the amplify/backend repo for this?

https://github.com/aws-amplify/amplify-backend/issues

elfin solstice Apr 15, 2024, 4:24 PM

#

will do - found the root cause in the end

#

Issue with parcelWatcher and latest version of node

#

https://github.com/parcel-bundler/watcher/issues/170

GitHub

Segmentation fault using wildcard in ignore option on Node.js v20.1...

Using * in the ignore option is causing a Segmentation fault when running on Node.js v20.12.x onwards. const watcher = require("@parcel/watcher") watcher.subscribe( process.cwd(), (err, e...

#

https://github.com/aws-amplify/amplify-backend/issues/1297

GitHub

Segmentation fault with `npx amplify sandbox` and latest version of...

Environment information System: OS: Linux 5.15 Arch Linux CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor Memory: 11.50 GB / 15.59 GB Shell: /usr/bin/zsh Binaries: Node: 20.12.2 - ~/.nvm/versions/n...

normal currentBOT Apr 15, 2024, 4:51 PM

#

✅ - Segmentation fault running sandbox

#✅ - Segmentation fault running sandbox