-
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
Fatal exception instead of Maximum call stack size exceeded #26829
Comments
Probably similar to #21591 and v8#8053. Accessing More general: const f = () => {
try{
f();
}catch{
console.log('A');
}
};
f();
setTimeout(() => console.log('B'), 250);
setTimeout(() => process.stdout.write('C'), 500);
setTimeout(() => require('fs').writeSync(1, 'D'), 1000); Expected: For this particular issue with async functions, I made a fix in |
It's not really about stdio, though, it would fail when doing 'use strict';
Promise.resolve().then(() => { // Or process.nextTick()
process.binding('tty_wrap');
// or cares_wrap, fs_event_wrap, http_parser, tls_wrap...
});
async function test() {
await test();
}
(async () => {
await test();
})(); We probably need to vet the |
That seems correct. The linked issues may then be unrelated, as it reproduces with other wrappers too. Fix in #26832 |
Fixes by 6fb32ac |
The following code causes an fatal exception for me (Node.js master):
I expected it to trigger
RangeError: Maximum call stack size exceeded
.The text was updated successfully, but these errors were encountered: