On May 21, 2010, at 8:54 AM, Keary Suska wrote:
> On May 21, 2010, at 9:18 AM, Paul Sanders wrote:
>
>>> Also be aware that just because memory is released, doesn't mean it is
>>> returned to the system (e.g. you will not
>>> see your apps memory usage go down in Activity Monitor). In fact, AF
Le 21 mai 2010 à 17:54, Keary Suska a écrit :
> On May 21, 2010, at 9:18 AM, Paul Sanders wrote:
>
>>> Also be aware that just because memory is released, doesn't mean it is
>>> returned to the system (e.g. you will not
>>> see your apps memory usage go down in Activity Monitor). In fact, AFAI
On May 21, 2010, at 9:18 AM, Paul Sanders wrote:
> > Also be aware that just because memory is released, doesn't mean it is
> > returned to the system (e.g. you will not
> > see your apps memory usage go down in Activity Monitor). In fact, AFAIK,
> > it is never returned to the system,
> > exce
> Also be aware that just because memory is released, doesn't mean it is
> returned to the system (e.g. you will not
> see your apps memory usage go down in Activity Monitor). In fact, AFAIK, it
> is never returned to the system,
> except perhaps in low memory situations.
I don't actually think
On May 20, 2010, at 9:37 PM, Nick Zitzmann wrote:
> On May 19, 2010, at 5:36 AM, Vassilis Pantazis wrote:
>
>> Hello,
>>
>> I have in my code the following statement:
>>
>> NSDirectoryEnumerator* dirEnum;
>> NSArray* inDirContents;
>>
>> dirEnum = [[NSFileManager defaultManager] enumerat
Hello Nick,
First of all thank you for your reply! My method has been monitoring the mem
usage of the specified (and other calls) while in the debugger and trusting
guard malloc for memory leaks. With this the mem allocated by the said call
is instantly in the scale of
tenths of MBs for just one l
On May 19, 2010, at 5:36 AM, Vassilis Pantazis wrote:
> Hello,
>
> I have in my code the following statement:
>
>NSDirectoryEnumerator* dirEnum;
>NSArray* inDirContents;
>
>dirEnum = [[NSFileManager defaultManager] enumeratorAtPath:inPath]; //
> inPath is a valid path
>inDirCon