High RAM usage (300mb) even though preview debug says 50mb

Problem Description

I'm using a placeholder project just to show the extreme amounts of RAM a simple example can use. The example provided in the preview debug says it's using just 50mb of memory, and when I export with Web Nodekit, it skyrockets to 300mb of memory used, in Windows 7 64 and OSX 64. That number is much, much bigger for my full project, where I only have 2 2048x1536 images, and 2 512x512. No other asset is more than 128x128. That project blows up to 1.1 gb of RAM memory used when exported and opened in Mac and Win, while the preview debug in C2 says less than 50mb usage.

Attach a Capx

Attached using Scirra forum upload attachment

Description of Capx

Simply shows 4 2048x1536 images. When you export to win64 using that .capx, the RAM usage is 300MB, when in preview, only 50mb

Steps to Reproduce Bug

• Step 1 - Preview and see RAM usage
• Step 2 - Export for Win and see RAM usage

Observed Result

Very high RAM usage on desktops

Expected Result

Either to use as much as preview debug says, or around that number, not 6x times more RAM.

Affected Browsers

• Chrome: (YES/NO)

Operating System and Service Pack

OSX with Parallels Windows 7

Construct 2 Version ID

Latest r195 with latest Web Nodekit

Just in case someone offers to help with this link, I've already gone through it https://www.scirra.com/blog/112/remembe ... our-memory <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

[attachment=0:1l0e4fni][/attachment:1l0e4fni]

Can't reproduce, says 13mb in Task Manager when I export here! If I add up the memory of all the processes it uses, it's more like 45mb. But you're comparing different measurements anyway: the C2 debugger tells you the estimated image memory only, whereas Windows is telling you the entire memory requirement of the full application (a complete browser engine), of which image memory is only one of many things using memory.

Ashley, so does it make sense that a video game which the debugger says only takes about 80mb when debugging, to take up 1.1gb of RAM when run via nodekit?

Should we state that configurations with less that 1.5 ram aren't supported by the game?

Well you're still comparing two different figures, the debugger is not taking in to account the rest of the processes' memory. Memory measurements at the process-level are complicated and approximate and I can't reproduce the problem anyway. How do you arrive at the 1.1GB figure? Are you adding up the sub-process figures or is that the total given by task manager?

Ashley

Here's a screenshot from the Activity app on OSX, I can provide one from WinXP if necessary.

Thankyou for caring and doing all this

I don't know, it might all just be cache. I don't think there's any reason to suspect a problem unless it causes a crash.

Is there any way to force clearing of cache?

Thanks again.