Re: Calling allObjects memory allocation problem

2010-05-22 Thread Clark S. Cox III
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, AFAIK, it

Re: Calling allObjects memory allocation problem

2010-05-21 Thread Vassilis Pantazis
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

Re: Calling allObjects memory allocation problem

2010-05-21 Thread Keary Suska
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] enumeratorAtPath:inPath];

Re: Calling allObjects memory allocation problem

2010-05-21 Thread Paul Sanders
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

Re: Calling allObjects memory allocation problem

2010-05-21 Thread Keary Suska
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, except

Re: Calling allObjects memory allocation problem

2010-05-21 Thread Jean-Daniel Dupas
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, AFAIK, it is

Calling allObjects memory allocation problem

2010-05-20 Thread Vassilis Pantazis
Hello, I have in my code the following statement: NSDirectoryEnumerator* dirEnum; NSArray* inDirContents; dirEnum = [[NSFileManager defaultManager] enumeratorAtPath:inPath]; // inPath is a valid path inDirContents = [dirEnum allObjects]; I have noticed that when the path

Re: Calling allObjects memory allocation problem

2010-05-20 Thread Nick Zitzmann
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 inDirContents =