Description
Version
v22.5.1
Platform
Linux linux 6.10.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 27 Jul 2024 16:49:55 +0000 x86_64 GNU/Linux
Subsystem
no modules were involved
What steps will reproduce the bug?
Open Node.js interactive mode by typing node in the terminal.
2. Enter while (false){} or while (false);.
- Notice the "undefined" display ready to be output.
- Enter
while (true);orwhile (true){}.- The terminal freezes and becomes unresponsive.
How often does it reproduce? Is there a required condition?
It reproduces 100% of the time, the required condition is that you're on node.js interactive shell.
What is the expected behavior? Why is that the expected behavior?
the expected behavior would be the return value of the block of code used in the while-loop, since 'while (false);' returned undefined, something predictably consistent is also expected with 'while (true);'
What do you see instead?
The terminal stops working until I kill the process manually with htop or kill command from another terminal.
Additional information
the issue is that in node.js interactive mode, when I type "while (false){}" or "while (false);" it will make a vague display of undefined ready to be output, sort of like a google suggestion. Now, here's the real deal issue: try typing "while (true);" or "while (true){}" instead. Your terminal will freeze and the only way to stop node.js at that point would be to kill the process with kill or htop. I think I know the reason behind the issue: the "semi-google-suggestion-like" vague display. Its purpose is it show you what is ready to be displayed when you press Enter, to save you ease and time by assuming that you likely are just wanting to glance at outcomes oftentimes. But to achieve this process of simulating the google-like output display, it has to execute the command in the background, and wait for the return result of executing that command, then send it to the vague display, therefore resulting in the bug that freezes your terminal when you type "while (true);" in interactive mode.