byebug tends to get "stuck" in the debugger in Windows Terminal with tabs

[ariccio]

Problem description

There are a number of situations that cause byebug to totally softlock when using the debugger on windows. In Windows Terminal, if I attempt to use tab autocompletion, byebug can get totally stuck, with no way to input new text, ctrl + c break out of it, is unresponsive to hitting enter, or really anything. I'm usually forced to kill the entire process! This seems to happen only in the Windows Terminal, so it may be a bug there. It seems to happen moreso in a rails app. If you cannot EASILY reproduce, I'll investigate much deeper, it's something wrong with something else.

Expected behavior

Autocompletion working normally, or at least byebug not completely soft locking.

Actual behavior

Completely stuck in a debugger prompt.

Steps to reproduce the problem

1. Start a rails app
2. Hit a code path with a byebug
3. Attempt to use tab autocompletion in the middle of some already entered text
4. Try to do anything else

[MarcoBomfim]

This seems to happen not only with byebug, but with pry as well. Not sure if it's a byebug issue, although I'm also looking for a solution for this.

[wujibear]

I have to essentially close my terminal tab each time. Such a pain.