You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you start a process and send it to the background, using node foo.js &, the terminal does something with the stdin that causes issues when using keypress.
It appears to freeze the whole node process (such that any ports you are listening on remain unavailable to the system but don't respond). The process itself doesn't respond to any signals except SIGKILL.
This is only the case when we've called process.stdin.setRawMode(true)
The system sends a SIGTTOU at some point after launching, but before becoming unresponsive. I'm wondering if I could listen for that signal and call keypress.disable(process.stdin) or something similar.
I'm using OS X 10.10.1 and this problem reproduces in node v0.10.x.
The text was updated successfully, but these errors were encountered:
When you start a process and send it to the background, using
node foo.js &
, the terminal does something with the stdin that causes issues when usingkeypress
.It appears to freeze the whole node process (such that any ports you are listening on remain unavailable to the system but don't respond). The process itself doesn't respond to any signals except SIGKILL.
This is only the case when we've called
process.stdin.setRawMode(true)
The system sends a SIGTTOU at some point after launching, but before becoming unresponsive. I'm wondering if I could listen for that signal and call
keypress.disable(process.stdin)
or something similar.I'm using OS X 10.10.1 and this problem reproduces in node v0.10.x.
The text was updated successfully, but these errors were encountered: