Is there a solution to the issue with hanging nwjs processes in test play?

[Trihan]

This happened with MV as well. Intermittently (though more often than not), after exiting a game in test play, an nwjs process is left behind that uses up all my CPU cycles. Has anyone else experienced this or found a solution to it?

I used to think it was to do with closing it via the "X" button in the menu bar rather than exiting the game via menu, but it happens even if I go the menu route.

 

[KurayamiBlackheart]

This happened with MV as well. Intermittently (though more often than not), after exiting a game in test play, an nwjs process is left behind that uses up all my CPU cycles. Has anyone else experienced this or found a solution to it?

Just opened taskmgr and no. Tho I do recall seeing the process persisting after closing a playtest. I think the process ends up closing itself just later on (maybe few seconds/minutes after).

EDIT : Tho if it persists on your side, you could always try to check the proprieties of the process and what not. If you're on Windows, install the program Sysinternals Process Explorer from Microsoft, it'll allows you to see way more details about every process active on your computer.

 

[Trihan]

Just opened taskmgr and no. Tho I do recall seeing the process persisting after closing a playtest. I think the process ends up closing itself just later on (maybe few seconds/minutes after).

Mine doesn't. It stays there until I manually end it. I've occasionally forgotten to check task manager and had rogue processes last for days, wondering why my PC is performing badly until I remember.

 

[KurayamiBlackheart]

What version of NWJS do you use ?

I seem to use 0.29.4

It might be due to a plugin in your project, or the version of NWJS, or something like this. Anyway it doesn't persist as a process on my side when I close a playtest.

 

[Trihan]

This didn't really help my understanding. XD

It happens in a blank project with no plugins, using MZ 1.4.3.

 

[KurayamiBlackheart]

Try to type this on the console: console.log(process.versions);

Also if you right-click a process, you can see the proprieties. You can see what the process is doing there.

If you use a newer version of NWJS, it might have to do with your game not closing properly, thus leaving a process of NWJS behind.

 

[Trihan]

I've figured it out. It happens if you close test play with the developer console open (which opens automatically on boot with VisuStella Core Engine with one of the parameters, which explains why I was seeing it so often). It should stop happening if I remember to always close the console first before the test play window.

 

[KurayamiBlackheart]

I've figured it out. It happens if you close test play with the developer console open (which happens automatically with VisuStella Core Engine with one of the parameters, which explains why I was seeing it so often). It should stop happening if I remember to always close the console first before the test play window.

Oh alright ahah. Now that you mention this, I think it might happen on my side if I leave the Super Tool Engine window of SRD opened while playtest. Tho the console of the game (the basic one) doesn't make a process persist if I close the playtest while letting it open, it just closes with it, without leaving something behind.

Anyway glad you figured out. It probably mean that the window of your plugin doesn't close itself afterwards if the game is closed (if it's related to VisuStella).

 

[Trihan]

Oh alright ahah. Now that you mention this, I think it might happen on my side if I leave the Super Tool Engine window of SRD opened while playtest. Tho the console of the game (the basic one) doesn't make a process persist if I close the playtest while letting it open, it just closes with it, without leaving something behind.

Anyway glad you figured out. It probably mean that the window of your plugin doesn't close itself afterwards if the game is closed (if it's related to VisuStella).

It's not specifically related to VisuStella, I was just seeing it often because I always had the console automatically opening on boot. If I open the console manually with no plugins, it happens then as well.

 

[KurayamiBlackheart]

It's not specifically related to VisuStella, I was just seeing it often because I always had the console automatically opening on boot. If I open the console manually with no plugins, it happens then as well.

Maybe it has to do with NWJS or MZ. I'm on MV, and I can't reproduce this issue if I close the game without closing the console beforehand. The console closes with the game and its process also closes.

 

[Trihan]

Maybe it has to do with NWJS or MZ. I'm on MV, and I can't reproduce this issue if I close the game without closing the console beforehand. The console closes with the game and its process also closes.

Interestingly I can no longer replicate it on MV, so maybe the cause of it happening there was something else.

Ah well, I've figured out why it's happening in MZ so I know how to avoid it now.

 

[Htlaets]

Yeah, this happened to me both in MZ and MV too. Good finding the reason it's happening, though.

 

[caethyril]

I've noticed this occasionally as well. However, leaving the console open when closing the playtest window (even if the editor has been closed before doing so) is not sufficient to reproduce the problem for me, with or without the VisuStella MZ library.

 

[Trihan]

I've noticed this occasionally as well. However, leaving the console open when closing the playtest window (even if the editor has been closed before doing so) is not sufficient to reproduce the problem for me, with or without the VisuStella MZ library.

Hmm, interesting. On my end at least, 100% of the reproducible occurrences have had the console open when I closed the game window, so I can't see it being anything else in my case.