Skip to content
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

RangeError Maximum call stack size exceeded on nodejs v17.9.0 #44913

Closed
kqvanity opened this issue Oct 7, 2022 · 4 comments
Closed

RangeError Maximum call stack size exceeded on nodejs v17.9.0 #44913

kqvanity opened this issue Oct 7, 2022 · 4 comments

Comments

@kqvanity
Copy link

kqvanity commented Oct 7, 2022

Version

17.9.0

Platform

Linux laptop 5.15.0-48-generic #54~20.04.1-Ubuntu SMP Thu Sep 1 16:17:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

N/A

What steps will reproduce the bug?

Run the following code snippet with nodejs version 17.9.0

const readline = require('readline')
const signal = new AbortController().signal

let interfaceInstance = readline.createInterface({
	input: process.stdin,
	output: process.stdout
})
interfaceInstance.question('Add your coins (timed answer) ', { signal }, (answer) => {
	console.log(answer)
	process.exit()
})
setTimeout(() => {
	signal.abort();
	process.exit()
}, 3000);

How often does it reproduce? Is there a required condition?

How often does it reproduce?

Always.

Is there a required condition?

Can't seem to get what that means

What is the expected behavior?

The abort signal terminates the open interface, without any raised exceptions.

What do you see instead?

 $ node readline-module.js 
Add your coins (timed answer) what
node:internal/readline/emitKeypressEvents:74
            throw err;
            ^

RangeError: Maximum call stack size exceeded
    at cleanup (node:readline:143:21)
    at cb (node:readline:147:7)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)
    at cb (node:readline:148:14)

Node.js v17.9.0

Additional information

No response

@Trott
Copy link
Member

Trott commented Oct 7, 2022

Node.js 17.9.0 is unsupported as of 4 months ago. Please update to 18.x. Running your code sample on the latest 18.x release (as well as the latest 16.x release), I get this error: ReferenceError: ac is not defined.

@Trott Trott closed this as completed Oct 7, 2022
@Trott
Copy link
Member

Trott commented Oct 7, 2022

(Closed in the hopes that this is fixed and not a bug in Node.js, but if I'm wrong about that, please comment or re-open. Thanks!)

@kqvanity
Copy link
Author

kqvanity commented Oct 7, 2022

I get this error: ReferenceError: ac is not defined.

Sorry about that. I've done a miniature edit to the snippet before submitting, and forget to rename this part too.

Node.js 17.9.0 is unsupported as of 4 months ago.

I did install another version i.e. v18.9.1, and it worked.

I was wondering if the docs mention such facts i.e. the schedule of the support cycle, and 'unstable' releases.

@Trott
Copy link
Member

Trott commented Oct 7, 2022

I was wondering if the docs mention such facts i.e. the schedule of the support cycle, and 'unstable' releases.

We might want to improve the wording, but there's a fairly prominent link on the home page of the nodejs.org website that says Long Term Support (LTS) schedule but it's really the full support schedule. (Scroll down for unsupported releases to see when they went in and out of support.)

Even numbered releases (14, 16, 18, etc.) are supported for much longer than odd numbered releases (which are only supported for around 8 months or something like that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants