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
Fix shutdown hang #37
Labels
upstream
Must be fixed in some dependency
Comments
This feels like a deadlock between waiting for events in two different places:
Next step should be to make a small repro and send to upstream, I'm guessing this is an upstream issue. Thread dumpConstructed using this trick.
|
walles
added a commit
that referenced
this issue
Apr 18, 2021
* Fixes #37 * Fixes #34 * Replaces #44 * Makes window resizing smoother. Before this change, the main loop was roughly: * Await one single user input event * Handle single user input event * Redraw screen With this change in place, the main loop is: * Await one single user input event (like before) * Handle single user input event (like before) * If there are no more events, redraw screen (new!) The difference is huge if you do a fling scroll on a trackpad. Before, scrolling was slow at constant speed, and the scrolling kept on at that slow constant speed way longer than what it should have. Now, scrolling feels just like it should.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Try this
moar
on a large fileq
while the mouse scroll is catching up (Avoid screen refreshes #34)Current result
moar
closes its display, but then hangs without giving any prompt back. Ctrl-C doesn't help, it has to be killed.Expected result
A clean exit.
The text was updated successfully, but these errors were encountered: