I got a reply on the nwjs issue post
Okay, I ran the test.
There's a TON of images that are being loaded, and they're probably going to stay loaded even when not in use.
And since there's so many images, it's using up a ton of memory.
Just a guess, though.
Unfortunately, this is a problem with Construct 2 loading too much.
Which can't be fixed without telling the Construct 2 developers to stop loading images in advance, and to unload images if they haven't been in use for a while.
So basically, there's nothing that can be done short of patching the output from Construct 2.
But the way it's laid out, you'd need to make a patcher program to do it, because every time the game is rebuilt it will need to be repatched, and as resources are added the line numbers will change.
Also, remember that the patch has to remove resources that aren't in use, or everything will just fail once enough stuff has loaded(as in, when someone is at a certain point through the game)
I'm 95% sure this is bollocks as C2 definitely should load images on a layout-by-layout basis. Or is that only for VRAM, and it loads all the images into RAM first as well? I think I don't have total understanding here as if images are loaded purely layout-by-layout, than this build should have loaded nothing at all, which is clearly not the case.
@Ashley what are your thoughts on this?
Ugh, I'm getting really sick of these constant struggles to get desktop export working