-
Notifications
You must be signed in to change notification settings - Fork 216
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
Sometimes slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10) #156
Labels
Comments
dbkaplun
changed the title
slap has one keystroke's worth of input lag on iojs and node 0.12 (but not 0.10)
Sometimes slap has one keystroke's worth of input lag on iojs and node 0.12 (but not 0.10)
May 2, 2015
dbkaplun
changed the title
Sometimes slap has one keystroke's worth of input lag on iojs and node 0.12 (but not 0.10)
Sometimes slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10)
May 2, 2015
dbkaplun
changed the title
Sometimes slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10)
~10% of the time, slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10)
May 2, 2015
dbkaplun
changed the title
~10% of the time, slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10)
Sometimes slap has one keystroke's worth of input lag on OSX iojs and node 0.12 (but not 0.10)
May 2, 2015
Bump |
See also nodejs/node-v0.x-archive#9310 and libuv/libuv#304. |
A fix has been merged into libuv. Soon! |
Looks like this issue was fixed with Node 0.12.5. Please confirm! |
@dbkaplun I am not in a position to confirm this slap bug for the next few months 😃 |
Closing. If issues continue, I will consider reopening. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe 10% of the time, when you're typing, the last keystroke isn't shown on the screen. After some debugging, I've found that the keypress is being registered, but stdout is simply not flushed. As it turns out, the whole event loop shuts down, i.e.
setInterval
callbacks stop getting called. However, as soon as I send any more data to stdin, the event loop works again andsetInterval
callbacks are called again, so it seems like a blocking read is the issue somewhere.The text was updated successfully, but these errors were encountered: