Problem Description____ I have built an desktop application (Quiz with animations between questions) which runs without incident in a browser, without any memory leakage, but when it's exported for Node Webkit it suddenly has a memory leak. Already checked to see if anything is causing this on my side but have found nothing. As soon as I start it up (task manager open), it starts leaking. So much so, that after a while it crashes.

Is this a problem with Node webkit? Or have I messed up?

Any answers or suggestions appreciated!

RegardsC ____

Attach a Capx____ Upload a Capx to this post ____

Description of Capx____ Concise description of what this CapX does ____

Steps to Reproduce Bug

Step 1

Step 2

Step 3 etc.

Observed Result____ Memory leaks when exported for Node webkit ____

Expected Result____ No Leak ____

Affected Browsers

Chrome: (NO)

FireFox: (NO)

Internet Explorer: (NO)

Operating System and Service Pack____Windows 7, Latest service pack ____

Closing, please only report issues with the latest version of Construct 2. If you are really using r158.2, then its version of node-webkit is going to be significantly older and with several known bugs that have already since been fixed.

Can't reproduce in r175 (which is using node-webkit 0.10.0-rc1) on Windows 8.1. Memory use appeared steady. Note it's normal with garbage collected languages that memory usage slowly increases, and then after some time it collects and goes back down again. That is what I observed. Perhaps you are mistaking that for a memory leak and the crash you saw was for a different reason?