Memory leak in t2dTileLayer objects (iTGB 1.4) [SOLVED]

#1 So, I figured out how to fix the memory leak:

=====================================
SOLUTION
=====================================
In the function:

bool t2dTileLayer::setLayerFile(void* obj, const char* data)

Comment out these two lines in both of the "else-if" blocks:

layer->deleteLayer();
layer->createLayer(1, 1, 1, 1);

=====================================
CAUSE
=====================================

It seems those two lines are unnecessary (for my purposes at least), as this call in that same block:

layer->loadTileLayer(data);

Will end up calling:

IMPLEMENT_T2D_LOAD_METHOD( t2dTileLayer, 3 )

Which ends up calling:

object->createLayer( tileCountX, tileCountY, tileSizeX, tileSizeY );

This means the second call to createLayer() is allocating mppTileObjectArray without freeing it first. So, I suppose another solution would be to call deleteLayer() before the createLayer() in that IMPLEMENT_T2D_LOAD_METHOD(), although the first seems pointless.

#2 I see that createlayer does not make a sense, but why would you not call delete unless you want a memory leak cause the old one is not gone?

#3 True. It is probably a good idea to put object->deleteLayer() before the call to object->createLayer(...) in that load method.

#4 @Richard,@Marc

Sorry for bumping this old thread,but I have a question.

In regards to the "Leaks" Instrument -- is this something within ITGB 1.41?
or is this something in Xcode?

Any Links or info about this would be appreciated.

#5 This is an Xcode tool.

http://developer.apple.com/library/mac/#documentation/Performance/Conceptual/ManagingMemory/Articles/FindingLeaks.html

#6 @Alistair

Thanks You. :D