Revision history [back]

This is not a real leak in the sense that you will run out of memory if you do some things over and over again. As far as I could gather, this seems to be by design see here and here (the second link describes a solution, but I am not good enough in c++ to work out the details) or google "static initialization order fiasco". You can reduce the number of things dumped if you force the program to unload the dll first, like so, e.g. in the ExitInstance() function of your app. Please note too, that I last used 3.10, I hope what I wrote is still up to date.

This is not a real leak in the sense that you will run out of memory if you do some things over and over again. As far as I could gather, this seems to be by design see here and here (the second link describes a solution, but I am not good enough in c++ to work out the details) or google "static initialization order fiasco". You can reduce the number of things dumped if you force the program to unload the dll first, like so, e.g. in the ExitInstance() function of your app. Please note too, that I last used 3.10, I hope what I wrote is still up to date.