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
By default, nw command waits for its main process termination to remain as the console's foreground process.
At this point, terminate it by Ctrl+C, nw's child processes are not killed and turn into zombies.
nw command invokes 3 or 4 processes.
After Ctrl+C termination, there remain 2 or 3 processes.
I think Ctrl+C would kill just the main process, and left 2~3 processes would be child processes.
On the other hand, terminating via GUI ❎ button works well to clean all the nw processes.
OS: Windows 8.1 Pro (x64)
Node.js: v8.11.3
nw: v0.31.4 (Both of normal ver. and SDK ver.)
💬 Executed $(npm bin)/nw on git bash
Do you have any better solution for this?
I sometimes got OS freeze by this, with nw zombies eat up memory (Horrible!).
In issue #9, they've talked about non-waiting nw execution.
Now I think this may help, at least (Avoid Ctrl+C itself, by making nw non-wait).
The text was updated successfully, but these errors were encountered:
By default,
nw
command waits for its main process termination to remain as the console's foreground process.At this point, terminate it by Ctrl+C,
nw
's child processes are not killed and turn into zombies.nw
command invokes 3 or 4 processes.After Ctrl+C termination, there remain 2 or 3 processes.
I think Ctrl+C would kill just the main process, and left 2~3 processes would be child processes.
On the other hand, terminating via GUI ❎ button works well to clean all the
nw
processes.$(npm bin)/nw
on git bashDo you have any better solution for this?
I sometimes got OS freeze by this, with
nw
zombies eat up memory (Horrible!).In issue #9, they've talked about non-waiting
nw
execution.Now I think this may help, at least (Avoid Ctrl+C itself, by making
nw
non-wait).The text was updated successfully, but these errors were encountered: