DLL Memory leaks

[Naftali]

Hello All,

We have a serious problem of memory leaks in our application that is caused because the fact that even when the application goes down the Dll's that it's using are still in the air (when we did restart to the computer the dll gave us an error message).
We want to know how can we see in the application which dll's are still in the air and how can we "kill" those dll's from inside of the application.

Thanks in advance,

Naftali.

 

[WilMead]

The nature of a library remaining "loaded" after user application exits does not necesarily constitute a memory leak. I'm not sure about the handling of implicitly loaded libraries, the ones you don't have a LoadLibrary call for.
But the help files for API calls below contain alot of information about how Dynamic libraries get used.
[tt]
Public Declare Function LoadLibrary Lib "kernel32" Alias "LoadLibraryA" (ByVal lpLibFileName As String) As Long

Public Declare Function LoadLibraryEx Lib "kernel32" Alias "LoadLibraryExA" (ByVal lpLibFileName As String, ByVal hFile As Long, ByVal dwFlags As Long) As Long

Public Declare Function FreeLibrary Lib "kernel32" Alias "FreeLibrary" (ByVal hLibModule As Long) As Long
[/tt]



Wil Mead
wmead@optonline.net