Originally Posted by
eska
The thing about the DTMs not freed is because of the new includes. I also get those on other scripts.
Now about the message about memory leaked, that's in the FreeAllMemory procedure, it display that if it fails to free one or more DTM. Usualy it will fail to free a dtm if it's already unloaded, which might be why it sometime log out even though there are lobster.
Now in my code, I do not free the lobster anywhere, except in the FreeAllMemory which is called only when the program close.
It should also be noted that even if this FreeALlMemory fails, it isn't a big deal. The dtms are very, very small in size, and the bitmap is less than 200kb
At most, 300kb are leaked if you recieve that message, so really it's nothing to worry about.
What I think is happening, is that there might be a leak somewhere in the SRL includes. 1.7gb simba process is way over the top.