load image from URL memory issue

Bugs will be moved here once resolved.

Post » Mon Sep 22, 2014 6:55 pm

Memory piles up when loading image from URL
When loading image and replacing current frame it doesn't free memory.

Attach a Capx
Attachment file.

CAPX is just Sprite that keeps loading one image
Press space to toggle loading on and off. Image is loaded from project files. I used Node-Webkit preview to see the nw process better on Windows Task Manager.
Updated CAPX 9/23/2014
Enter to go different layout and back.

Steps to Reproduce Bug
  • Open Windows Task Manager
  • Run preview
  • Press space
  • Observe building up memory on nw.exe

Observed Result
Building up memory on nw.exe until crash.

Expected Result
No piling up memory usage when replacing image. If possible.

Affected Browsers
  • Node-Webkit: YES (Easier to track memory usage)
  • Chrome: Not sure apparently NO
  • Firefox: Not sure apparently NO

Operating System and Service Pack
Win 7 Ultimate SP1

Construct 2 Version ID
180 64-bit
You do not have the required permissions to view the files attached to this post.
Last edited by Katala on Tue Sep 23, 2014 3:11 pm, edited 1 time in total.
B
34
S
9
G
3
Posts: 517
Reputation: 5,276

Post » Tue Sep 23, 2014 2:13 pm

Ok I think this is Node-Webkit specific. It does't happen on NW version 0.8.6. Maybe I should make new topic about this to somewhere else?

Also tested on C2 version 181 which uses node webkit 0.10.5 and it has same issue.
B
34
S
9
G
3
Posts: 517
Reputation: 5,276

Post » Tue Sep 23, 2014 2:18 pm

Might make sure you have webgl working.
I would think that switching layouts would prove that... other than using the conditions that is.
Image ImageImage
B
172
S
50
G
183
Posts: 8,439
Reputation: 115,597

Post » Tue Sep 23, 2014 2:36 pm

Might make sure you have webgl working.
I would think that switching layouts would prove that... other than using the conditions that is.

Renderer expression shows webgl. Problem doesn't occur on canvas2d. Not sure how I prove that changing layout.
B
34
S
9
G
3
Posts: 517
Reputation: 5,276

Post » Tue Sep 23, 2014 2:43 pm

Well changing layout in webgl should free memory.
That would solve the issue, and theres a high probability that may be the only solution.
Image ImageImage
B
172
S
50
G
183
Posts: 8,439
Reputation: 115,597

Post » Tue Sep 23, 2014 3:30 pm

Well changing layout in webgl should free memory.

It doesn't free memory. I exported this and replased it to use Node-Webkit v0.8.6 and I don't see any issues there.

Node-Webkit v0.8.6 exe
B
34
S
9
G
3
Posts: 517
Reputation: 5,276

Post » Thu Sep 25, 2014 2:15 pm

I can't reproduce in Chrome 37, but it does reproduce in node-webkit. I'm not sure why it would happen since the code is short-circuited to basically do nothing if you load the same image URL as is already loaded.

This may be a Chrome 35 bug which is fixed in Chrome 36/37, so it may be that a future node-webkit update will have it fixed. If not try reporting it again but directly to node-webkit (https://github.com/rogerwang/node-webkit/issues) since if it doesn't show up in Chrome it's likely a NW specific issue and not a C2 bug. Alternatively the workaround is simple too, just don't repeatedly load the same URL.
Scirra Founder
B
402
S
238
G
89
Posts: 24,632
Reputation: 196,041

Post » Thu Sep 25, 2014 2:52 pm

If not try reporting it again but directly to node-webkit (https://github.com/rogerwang/node-webkit/issues) since if it doesn't show up in Chrome it's likely a NW specific issue and not a C2 bug.

Will do that.
B
34
S
9
G
3
Posts: 517
Reputation: 5,276


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest