I wonder if it is possible to prevent them by using SetProcessWorkingSetSize or any equivalent ?
Posted on 2002-07-20 00:48:09 by Axial
I think the reason for leaks is mainly that the reference count
is not decremented for the DLLs, thus they will not be unloaded.
Posted on 2002-07-20 06:58:53 by f0dder
that happens to me sometimes, when i am developing dll's and when i quit exe that loads that dll, dll still remain in memory although that exe was the only program that loaded that dll
then i have to restart windows

so is there anyway to unload that dll manualy, for instance to find that count for specific dll and decrement it manaly or some other way?
Posted on 2002-07-20 16:54:03 by Mikky
As I've read from previous posts, Windows keeps the DLL reference count in a structure pointed by HINSTANCE (hLibrary I guess?). As this question about DLL reference counts has been asked many times, maybe we should put it in FAQ?
Posted on 2002-07-20 17:01:49 by comrade
Anyone knows a solution for this? If yes, please post some source :)
It will be more usefull for the FAQ if it contains a answer to the
frequently asked question ;)
Posted on 2002-07-20 18:01:37 by bazik