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
Alacritty stops responding shortly after first few keyboard strokes on Mac OS #1803
Comments
Some keyboard combinations halt the I/O of a terminal emulator. Just to make sure: Executing Ctrl+C does not give back control, right? And Ctrl+D does not close Alacritty? |
Neither of those combinations give back control, or even show up as a received |
@pault-t-canva does CPU consumption jump to 100%? Are you able to repro in the window example in winit? |
Ah, looks like the issue definitely lies in winit. What's happening when i run the window example is the log shows the correct events coming through. Then if i type a few keys in relatively quick succession, it keeps replaying these events even though I have stopped typing keys. Basically those keys never appear to get off the event queue for some reason |
Should I close this and open an issue on winit? |
If you'd open an issue with winit, that would help a lot. But you can keep this one open to track the problem for others. Just share a link to the winit issue here so everyone can follow the progress. |
Which operating system does the issue occur on?
MacOS Sierra 10.13.6
When running from d68ecb0, I find that the running Alacritty only appears to work for the first few seconds. Weirdly enough, it only starts to fail if I type more than around 5 characters within approximately 5 seconds. Anything slower than that it appears to stay healthy. When it fails, the debug output stops completely, and it starts to not respond to anything at all. It does not recover.
The following is a log from running alacritty with
-vvv
and--print-events
.The
alacritty.yml
file is the default osx copy from the repository with no changes.I'm happy to do any debugging that may help
The text was updated successfully, but these errors were encountered: