-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
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
test: test-async-wrap-pop-id-during-load failure on mac #20888
Comments
I have not seen it before. |
just got a similar failure on AIX https://ci.nodejs.org/job/node-test-commit-aix/15241/nodes=aix61-ppc64/consoleFull |
Great, I'll take a closer look. Thanks |
On my laptop, if I use |
Yep, it works if I revert that commit. |
Minimal reproduce. Analysis for AIX is posted in #20688 same applies for MAC too, though with a different stack size (fluctates between systems and other load factors I guess) #cat 20888.js function fn() {
fn();
}
async function foo() {
await fn();
}
foo() #node 20888.js (node:69273) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at fn (/home/gireesh/20888.js:1:74)
...
(node:69273) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error ... #echo $? (node:69278) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
at fn (/home/gireesh/20888.js:1:74)
(node:69278) UnhandledPromiseRejectionWarning: Unhandled promise rejection...
#echo $?
0 #node --stack-size=40 20888.js internal/bootstrap/loaders.js:91
const ContextifyScript = process.binding('contextify').ContextifyScript;
^
RangeError: Maximum call stack size exceeded
at bootstrapInternalLoaders (internal/bootstrap/loaders.js:91:36) #echo $? |
FWIW, I just ran tests locally for #20916 and nothing failed. |
was this observed since the last report (in May)? looks like no to me. |
If it's not reported here, it's unlikely anyone is going to remember having observed it, so you can tentatively assume "No, it has not been observed since." |
closing, as this does not look like has been observed since. Please re-open if that is not the case |
I'm seeing the following test failure when running on mac os x:
It is sort of hard to see what the issue is by looking at the above output but adding log statement (or start with lldb/gdb) to see
stderr
I can see:This can be reproduced/simplified by running
This error originates from
node.cc
when trying to compile theinternal/bootstrap/loaders.js
backtrace
I don't see this error on the CI servers and wanted to bring this up and ask if anyone else has seen this?
The text was updated successfully, but these errors were encountered: