Node process freezes when text is selected in command line

[reverofevil]

• Version: v16.2.0
• Platform: Windows 10
• Subsystem: -

What steps will reproduce the bug?

• Run any Node.js script: an http-server or long-running npm install.
• Select text in console window.

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

Always.

What is the expected behavior?

Node process should never freeze due to text selection in terminal, same as desktop application UI threads should never stop execution of application.

What do you see instead?

Server doesn't respond to requests, npm installation freezes. Whole node process does nothing.

Additional information

This is Windows-specific problem that I encountered by interacting with terminal window in a different way more than 3 years ago. Given that it's very easy to start selection on Windows just by clicking a terminal window (while switching windows, for example), it's very common to find a long-running script doing nothing after several minutes of waiting for progress. I think this is a serious UX issue.

[Trott]

@nodejs/platform-windows

[targos]

This seems to only happen with conhost.exe.

[nikikalwar]

Hi All, I am interested with node process object, can I pick this up for investigation?