Apparently a well known problem in the NW.JS community. O_o
Still not fixed since forever. Jesus, we just can't get a break... bloody Google broke vsync for ages and then this. Forget about making large games, even for PC. gg
https://github.com/nwjs/nw.js/issues?ut ... emory+leak
What this means is that bigger C2 games can only be played in short sessions. After awhile the memory leak grows unstable, the first symptom is stutter in gameplay, that gets worse and worse. The smaller the game, the longer the play session, but all games suffer this problem.
This is literally C2-breaking for any export reliant on Chromium. The problem is worse for bigger games as the play session before issues arise can be ~1 hour.
This was posted awhile ago, it's still present and a problem for bigger games with lots of assets.
The reason I am posting this again is because it is a major problem that still has not been resolved for over a year.
Attach a Capx
More info in above thread
Description of Capx
More info in the above thread
Steps to Reproduce Bug
- Make an empty layout with a few 2048 x 2048 empty sprites.
- Repeat with a few of such layouts.
- Switch between them.
Layout transitions increase the cache memory used in Chromium/NW.js, repeatedly rising until game stutters or system crash. Observe the nw.exe or chrome.exe using more and more memory.
This problem DOES NOT occur in IE.
No memory leak.
- Chrome: YES
- FireFox: N/A
- Internet Explorer: NO
Operating System and Service Pack
Win 7 64 SP1
Construct 2 Version ID