Have you a code showing the actual problem you are facing.
Potentially you are using some chain calling to that method which might show similar issues to the ones suggested above but due to a different root.
Haven't had any freeing problems so far I've to say.
The only one I tend to run into quite too often is when I use TLinks on classes for fast removal from the list again and forget to make my destroy method null-ifying the tlink. in that case the object will never be freed.
Oh and just to make sure: global variables operate on the reference count differently than locals ... means they don't imidiate free
Potentially you are using some chain calling to that method which might show similar issues to the ones suggested above but due to a different root.
Haven't had any freeing problems so far I've to say.
The only one I tend to run into quite too often is when I use TLinks on classes for fast removal from the list again and forget to make my destroy method null-ifying the tlink. in that case the object will never be freed.
Oh and just to make sure: global variables operate on the reference count differently than locals ... means they don't imidiate free