> I see now that the 2 processes using 90MB RAM, after i left the game open (just open a lvl and stay idle) for about 30min it went up to 600MB RAM!
> So i guess that is my problem..
>
> I will try --single-process arg but i dont think it will make any change.
>
> Any other arg or some setting in NWjs or C2 to solve this problem?
>
Single processing is broken (again) in the recent releases.
This sounds more like an eventing problem to me as well and the increasing amount of memory usage is probably related to audio files being loaded into memory (if you don't load everything into memory on start). You should debug your project and closely watch for suspicious and unusual behavior.
Very old versions of NW.js had a problem like this as well, so testing this out using a more recent version might help.
Thanks for the reply,
I have removed many "for each" and "every tick" events and excluded audio from save along with some other minor tweaks.
I also used --single-process.
So far it looks fine. Ive played from start to finish with no problems and also someone who had the issue did not have it now.
I hope it got fixed.