So I've had a hunch that it's my use of video that results in poor performance and lagspikes in Klang. I made this little stress test to see how the video object works across layouts, and it seems like a played video is a burden for the remaining of the play session. I easily got this empty project with one 5 sec video file to take 7gb of ram on firefox64 bit, and I crashed NW.js preview. The memory never seemed to get cleaned either. The video doesn't even stop playing between layouts, so if you press f1 and f2 continiously it feels like 20 videos playing on top of each other. THIS IS BAD!!!
One important difference to notice here though. In FIrefox the video stops playing every time I change the layout. This explains why I don't really have this bizarre frame skips and slow downs when I play the game in Firefox. In NWjs though the video champs on to the next layout, and even stacks with a new video instance if I go back.
Considering how my game runs on NWjs, and uses lots of video, I can only point fingers to this and blame this. It just makes too much sense considering all the performance drop patterns I've seen in game
Chrome manages to clean itself faster than I can raise the memory level. The video also stops. This is a NWjs issue.
Attach a Capx
https://drive.google.com/file/d/0B1n4Fd ... sp=sharing
Description of Capx
Play it in NW.js
Steps to Reproduce Bug
- run the game in preview and open the task manager
- press f1 and f2 continiously
- watch the mayhem, and keep doing it till the browser crashes.
Memory use through the roof, videos don't stop between layouts on NWjs. I get a feeling they never stop being a burden to the playsession
I'm expecting the video to stop when changing the layout, and restart with only 1 instance when I return to layout1.
- Chrome: (NO)
- FireFox: (YES)
- NWjs: (YES!!!)
Windows 7 service pack 1
Construct 2 Version ID
233 (newest as of 10.08.2016