Adobe AIR Development

[zezke]

Hi,

I was wondering if there was a way to monitor how much memory my app currently uses. I process a lot of images and I don't want to end up with a heavy load app.

Thank you

[JRab · Accepted solution]

hey zezke,

you can probably get a good feel for the amount of memory in use by Adobe AIR (all instances i believe) by using the System.totalMemory property of the System class which is in the file.System package. Here's more info about this feature:

http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/system/System.html#totalMemory

hope that helps. good luck!

[zezke]

Thank you for helping me (again).

[JRab]

hah dont sweat it! if you have anymore questions we'll be more than happy to help you out

[alexbevi]

I know this is marked as solved, but check out http://code.google.com/p/mrdoob/source/browse/trunk/libs/net/hires/debug/Stats.as?r=125

I personally use this in all my projects during development.

usually I have a component as the last element in my display list that I attach it to

<mx:UIComponent id="debug" top="0" left="0" />

so if you use the same example, just add the following to your applicationComplete handler:

 debug.addChild(new Stats());

[zezke]

Nice addition, I will definitely try this. Thank you.

[alexbevi]

I'm sure you'll find this yourself pretty quickly, but I posted a link to the wrong changeset

This is the latest one at the moment: http://code.google.com/p/mrdoob/source/browse/trunk/libs/net/hires/debug/Stats.as?r=236

[peter9477]

I'm not sure why you wouldn't just drop the revision as it should then always point to the latest: http://code.google.com/p/mrdoob/source/browse/trunk/libs/net/hires/debug/Stats.as (Oh, and thanks for the link.)

[zezke]

Are you guys sure this information is accurate? When I load several images in my application the memory usage does not increase.

[peter9477]

Memory usage in modern systems isn't straightforward sometimes.  Memory is often allocated from the operating system in large chunks (like megabytes at a time sometimes) which are then managed within an application.  Memory that is "released" is not necessarily returned to the overall pool until an application ends, and so forth.  Memory allocation for embedded assets may be done as the app launches, rather than during what you think are calls to "add" images.

If you allocated many megabytes and still see no change, I'd be inclined to agree that some of those calls are not being helpful, though you didn't say exactly what you're doing so it's hard to say.