Well - like I've said before - its not a malloc|free issue, I have taken great pains to search through the code as you all suggested - I did, and nowhere in the code do I call more mallocs than frees, and nowhere do I allocate memory that cannot be de-allocated *before* a branching instructions occurs - the allocations are all in tiny local functions like ones which manipulate text and so forth - there are no branching instructions anywhere near my mallocs. It - therefore - has to be a GDI leak, that is the only conclusion I can reach from studying the code in this manner. I have gone to great lengths to track down this elusive leak - which I admit - is an error on my part, and still no success - I have even tried the suggested option of removing all the drawing code - which does not even slow the leak down, no, it's somewhere in here with some other code that gets called by some other code which was called by some other code which was called by some other code in my program.... As you can see - its going on two days, and I still haven't gotten any closer to finding my error.... Im considering rewriting this whole program in Java...:laugh:
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day
