We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
master
uname -a
async_hooks
'use strict'; const { AsyncLocalStorage } = require('async_hooks'); const als = new AsyncLocalStorage(); function run(count) { if (count !== 0) { return als.run({}, run, --count); } } run(1000);
It's enough to run this script with node --stack-size=100 async-hooks-crash.js.
node --stack-size=100 async-hooks-crash.js
Always
RangeError: Maximum call stack size exceeded should be reported in the crash output:
RangeError: Maximum call stack size exceeded
$ node --stack-size=100 async-hooks-crash.js ... RangeError: Maximum call stack size exceeded ...
$ node --stack-size=100 async-hooks-crash.js Error: async hook stack has become corrupted (actual: 111, expected: 70) 1: 0x97e352 node::AsyncHooks::pop_async_context(double) [node] 2: 0x979587 node::AsyncWrap::PopAsyncContext(v8::FunctionCallbackInfo<v8::Value> const&) [node] 3: 0xbe369b [node] 4: 0xbe4c46 [node] 5: 0xbe52c6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node] 6: 0x13ff259 [node]
This issue was observed in CI runs for #34573 and #35779
Refs: #15448 (the condition is different and that issue was fixed a long time ago)
The text was updated successfully, but these errors were encountered:
I can't reproduce this with latest 14, 16 and 17 versions. But it is still reproducible with 12.22.8
Sorry, something went wrong.
Closing this issue because v12.x goes EOL at the end of this month and no more releases are planned.
No branches or pull requests
Node v14.15.0 (also reproducible on
master
, 831f4c7)Linux (
uname -a
: Linux apechkurov-laptop 5.4.0-52-generic Fix for path.resolve containing relative path to another drive in windows #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux)async_hooks
What steps will reproduce the bug?
It's enough to run this script with
node --stack-size=100 async-hooks-crash.js
.How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
RangeError: Maximum call stack size exceeded
should be reported in the crash output:What do you see instead?
Additional information
This issue was observed in CI runs for #34573 and #35779
Refs: #15448 (the condition is different and that issue was fixed a long time ago)
The text was updated successfully, but these errors were encountered: