Repository navigation
"clearImmediate" results in an abort #37806
Copy link
Copy link
Closed
Labels
confirmed-bugIssues and PRs for confirmed bugs.Issues and PRs for confirmed bugs.replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().Issues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
Description
Activity
- addedreplIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().Issues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
on Mar 19, 2021 It seems to be REPL only, the process doesn't crash when executing a file or using eval.
$ node -e 'clearImmediate({hasRef: true, _onImmediate: 100000000000000000})' internal/timers.js:278 item._idleNext._idlePrev = item._idlePrev; ^ TypeError: Cannot set property '_idlePrev' of undefined at ImmediateList.remove (internal/timers.js:278:30) at clearImmediate (timers.js:324:18) at [eval]:1:1 at Script.runInThisContext (vm.js:133:18) at Object.runInThisContext (vm.js:310:38) at internal/process/execution.js:77:19 at [eval]-wrapper:6:22 at evalScript (internal/process/execution.js:76:60) at internal/main/eval_string.js:23:3
I'm able to reproduce the crash on master branch when executing the given instruction on REPL.
- addedconfirmed-bugIssues and PRs for confirmed bugs.Issues and PRs for confirmed bugs.
on Mar 19, 2021 - added a commit that references this issue
on Mar 28, 2021 - added 2 commits that reference this issue
on Mar 29, 2021 - added a commit that references this issue
on May 1, 2021
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues and PRs for confirmed bugs.Issues and PRs for confirmed bugs.replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.timersIssues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().Issues and PRs related to timers, setImmediate(), setInterval(), and setTimeout().
What steps will reproduce the bug?
Setup a node instance,
and run the following javascript code.
Then an abort occurs.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.
What do you see instead?
Additional information