-
Notifications
You must be signed in to change notification settings - Fork 127
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
Debug freezes after a few keystrokes #934
Comments
Same reason here. Check this #871 (comment). It helped me too. |
Thanks for the tip @woto, exporting As discussed in the comment you linked, the problem seems to come from the |
Thank you for survey. I want to wait the next release of reline. |
I'm afraid this is not a If we use a simpler repro I mentioned in this comment with the latest |
I think I was hit by this, and spent several weeks in agony due to "random" freezes. Now trying this "RUBY_DEBUG_NO_RELINE" workaround (and crossing fingers that it will resolve my problem with docker container). Perhaps you should put this workaround as default option, and to get away from workaround behind env var instead (likely less time lost by random people around the world...) |
Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
`ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout.
(ruby/reline#580) Timeout's implementation relies on Thread, which would conflict with `ruby/debug`'s thread-freezing implementation and has casued issues like - ruby/debug#877 - ruby/debug#934 - ruby/debug#1000 This commit avoids the issue by completely removing the use of Timeout. ruby/reline@d4f0cd3fe1
Hi folks, could you try updating |
Awesome. Looks like it fixed! |
sounds, marvellous [insert trumpet fanfare and confetti here], need to try it when possible |
Your environment
ruby -v
: ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [arm64-darwin21]rdbg -v
: rdbg 1.7.1Describe the bug
Debugger is freezing after typing a few keystrokes at random; almost reliably freezing with 3+ keystrokes. Any new key pressed just echoes in the screen the key pressed, but nothing happens.
It freezes the terminal window so bad that not even CTRL C can escape it:
To Reproduce
Just install a debugger anywhere in the code and start typing on the console.
Expected behavior
I expected it not to freeze.
If I use binding.pry instead, everything works just fine.
Additional context
Rails application (7.0.4.3)
The text was updated successfully, but these errors were encountered: