resource busy or locked when relaunching NW.js in dev mode about haruneko

[Sheepux]

make sure you don't run it with administrator priviledge first.
(note: i don't get this error on windows and i'm restarting the client quite a lot)

[manh21]

Are there any background jobs by chance? I just found that nw.js hasn't closed properly, it still has a background process that ate about 6GB of my ram

make sure you don't run it with administrator priviledge first. (note: i don't get this error on windows and i'm restarting the client quite a lot)

this should not make any difference

[Sheepux]

As a security measure, make sure to never run hakuneko with admin priviledge. If a connector has a flaw a malicious website could cause a mess (never happened).
The only time i had a background process was the splash screen still being hidden and didn't display the main window, but here you seem to be able to close the process by yourself, so ... no idea so far.

[Sheepux]

I can confirm that i get it as well.
Mostly when exiting from VScode (not from the app), hakuneko is closed but nwjs is still running in the process list.

NW is missing a terminating signal handler ?

[Sheepux]

Hasn't happened to me for a good while (was something fixed in NWjs ?).
I'll close the issue but will reopen if someone encounters it again.