Aaron Ardiri wrote:
>>>
this is my code:
---
programData = MemPtrNew(imageSize);
....
MemPtrFree(programData);
---
there is NOWAY it misses the MemPtrFree call.. if it does, then the
program has crashed (before it).. and it does not do this.
<<<
Odd indeed, although I haven't tried duplicating this myself. I've seen
a similar problem on a different platform. In that particular case, it
turned out that the memory was being freed, but was still marked
"dirty." By allocating and freeing in a tight loop, the OS never got a
chance to do it's maintenence thing. Just a theory...
Michael Yam
Y Technology, Inc.
http://www.ytechnology.com
[EMAIL PROTECTED]
