Amplify-cli: Check failed: stack_overflow().

Created on 10 Oct 2019 · 9Comments · Source: aws-amplify/amplify-cli

Describe the bug
I updated the amplify cli today (version 3.12.0) and now get an error when attempting to run amplify storage update

The full error is:

⁠

⁠ Fatal error in , line 0

⁠ Check failed: stack_overflow().

⁠

⁠ FailureMessage Object: 0x7ffeefbfcc10Illegal instruction: 4

To Reproduce
npm install -g @aws-amplify/cli
amplify storage update

Expected behavior
The command works as expected

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: macOs Catalina
Browser: n/a
Version: 3.12.0

Additional context
Running amplify status or amplify env checkout .... commands work fine

bug storage

Source

danhumphrey

👍3

Most helpful comment

We released a new version last night, v3.15.0.
Please install the latest version and check if you are still having the issue.

UnleashedMind on 15 Oct 2019

🎉4

All 9 comments

Working in 3.11.0

mattk- on 10 Oct 2019

@danhumphrey what version of NodeJS do you have running?
@mattk- are you using this with catalina?

yuth on 10 Oct 2019

@yuth I'm running 11.6.0

danhumphrey on 10 Oct 2019

I just upgraded to Catalina, [email protected] and I'm seeing this with amplify api update as well:

#
# Fatal error in , line 0
# Check failed: stack_overflow().
#
#
#
#FailureMessage Object: 0x7ffeefbfdc90[1]    22391 illegal hardware instruction  amplify api update

Downgrading to 3.11.0 restores functionality.

warrenmcquinn on 11 Oct 2019

This is a very strange bug, I did reproduce it with our latest version as well (Amplify-CLI v3.13.0), it's also inconsistently popping up for node version 10.16.2 and 10.16.3 (LTS) too.
But it's working fine for node version 12.11.1 (latest version).

I've logged a issue on node github repo.
https://github.com/nodejs/node/issues/29939
For now, try to use the CLI on node version 12.11.1.
We will continue to monitor this bug, and keep you updated.

UnleashedMind on 12 Oct 2019

Also happening for me on 3.14.0. There's not an update without something breaking, doh...

houmark on 12 Oct 2019

We released a new version last night, v3.15.0.
Please install the latest version and check if you are still having the issue.

UnleashedMind on 15 Oct 2019

🎉4

v3.15.0 works for me on MacOS Catalina, node v12.8.0! Thanks!

warrenmcquinn on 15 Oct 2019

I know this issue is closed and I don't want to nerco it but I wanted to add that I was 3.14.0 on Windows and was experiencing this issue. Updating to 3.15.0 fixed it. Thanks for the quick fix!