flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Dahmen <fr...@dahmenia.de>
Subject Re: SkinnablePopupContainer.open() -> close() -> increases System.privateMemory
Date Fri, 06 Dec 2013 08:51:03 GMT
Thanks,

seems to work when i call gc() on close

but i read that one shouldn't do that and as i understand it shouldn't 
be necessary

because if it can be destroyed it will be destroyed

but in fact calling it keeps memory down, not calling it increases memory




Am 06.12.2013 09:35, schrieb Thiago Maia:
> Hello Frank
>
>    I usually do in this way to dont increase the memory
>
> PopUpManager.removePopUp(this);
> flash.system.System.gc();
>
> regards
>
> Thiago Maia
> a00s@a00s.com
> On 12/6/2013 12:16 AM, Frank Dahmen wrote:
>> Hi,
>>
>> see subject, i think I've cleaned up the popup
>> i also did a test with a clean (empty) SkinnablePopupContainer.
>>
>> privateMemory goes up, not eyery time, so i think it can be 
>> destroyed.... but only sometimes????
>>
>> opened and closed 10 times:
>>
>> System.privateMemory: 53784576
>> System.privateMemory: 54345728
>> System.privateMemory: 54910976
>> System.privateMemory: 55443456
>> System.privateMemory: 54837248
>> System.privateMemory: 55447552
>> System.privateMemory: 55934976
>> System.privateMemory: 56307712
>> System.privateMemory: 56418304
>> System.privateMemory: 56414208
>>
>>
>> or is System.privateMemory not the right value to look at?
>>
>> thanks
>>
>>
>>
>
>
> ---
> This email is free from viruses and malware because avast! Antivirus 
> protection is active.
> http://www.avast.com
>


Mime
View raw message