GetOpenFileName memory leak?

[Scott Penner]

I've been using the GetOpenFileName function from comdlg32.dll and I've noticed that the size of my app in memory jump about 2 MB after making the call.

This memory never seems to be released. Is there any reason why my app doesn't release the memory?

I've noticed the same things when using the common dialog control instead of the API function. But, it somehow made more sense to me then because I assumed that the control wasn't releasing the memory

Any ideas?

[Vlatko]

The memory usage of your app has increased because it is using the comdlg32.dll and it has to be read into memory. If you use the AX control then your app will still use the dll and as a 'bonus' it will use the ocx file.

[Megatron]

If you are loading it via LoadLibrary, then you can free it with FreeLibrary.

[Scott Penner]

That makes sense.
Thanks!