____ 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!
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.
____ Memory leaks when exported for Node webkit ____
____ No Leak ____
- Chrome: (NO)
- FireFox: (NO)
- Internet Explorer: (NO)
Operating System and Service Pack
____Windows 7, Latest service pack ____
Construct 2 Version ID
____ 58.2 (64bit) ____