Memory Leak with Node-Webkit

Bugs will be moved here once resolved.

Post » Mon Jul 21, 2014 1:52 pm

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!

Regards
C ____

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 ____

Construct 2 Version ID
____ 58.2 (64bit) ____
B
3
Posts: 7
Reputation: 189

Post » Mon Jul 21, 2014 2:18 pm

Are you really still using C2 r158.2?

If so, try at least the latest stable release r173, or even r175beta to see if the problem still exists.

Node-Webkit has probably been updated numerous times since r158.2, so it's worth testing with a more upto date release.
If your vision so exceeds your ability, then look to something closer.
Moderator
B
134
S
30
G
84
Posts: 5,393
Reputation: 58,468

Post » Mon Jul 21, 2014 4:42 pm

You'll also need to upload a capx or nobody will be able to help I'm afraid
B
92
S
31
G
24
Posts: 3,191
Reputation: 32,679

Post » Tue Jul 22, 2014 8:42 am

Thanks guys

Updated to the latest version but unfortunately the problem persists.
I have attached the capx file of the welcome screen. Please use discretion as it is a client project.

Any ideas? Thanks
You do not have the required permissions to view the files attached to this post.
B
3
Posts: 7
Reputation: 189

Post » Tue Jul 22, 2014 12:03 pm

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.
Scirra Founder
B
395
S
233
G
88
Posts: 24,376
Reputation: 193,852

Post » Tue Jul 22, 2014 12:33 pm

@Ashley
I checked his .capx and he's using r173 stable. (!?)
If your vision so exceeds your ability, then look to something closer.
Moderator
B
134
S
30
G
84
Posts: 5,393
Reputation: 58,468

Post » Tue Jul 22, 2014 12:54 pm

What zenox98 said, I've updated to the latest version of Construct. Same problem persists.
B
3
Posts: 7
Reputation: 189

Post » Thu Jul 24, 2014 3:29 pm

Any ideas? Anyone?

Thanx
B
3
Posts: 7
Reputation: 189

Post » Thu Jul 24, 2014 4:48 pm

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?
Scirra Founder
B
395
S
233
G
88
Posts: 24,376
Reputation: 193,852

Post » Thu Jul 24, 2014 5:34 pm

Hey Ashley,

Have you tried leaving it on overnight? The application currently runs on a kiosk type device and eventually crashes it. It's unfortunately not feasible to have somebody reset it every day.

Surely the GC will start destroying objects before it uses 4gb of memory? This is how much it ends up using on the kiosk devices before the device becomes unresponsive.

It is possible that something else is causing the crash, however, the team which is maintaining the kiosk have told us that nothing else is running on them (apart from OS related services).
B
3
Posts: 7
Reputation: 189

Next

Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 4 guests