It's probably not a memory leak. It has to do with the way memory is handled in Max.
When you free an object the memory is flagged as available the next time you call flushmem(), but it isn't given back to the system. If you call remove() and then AddLast() without flushing the memory in between new memory will be allocated becaus the old memory is still considered occupied.
Look at http://www.blitzwiki.org/index.php/FlushMem
When you free an object the memory is flagged as available the next time you call flushmem(), but it isn't given back to the system. If you call remove() and then AddLast() without flushing the memory in between new memory will be allocated becaus the old memory is still considered occupied.
Look at http://www.blitzwiki.org/index.php/FlushMem