🚀 go-pugleaf

Thanks. Now I have a brief idea of what might be wrong with the skinning
components I bought. MemProof reported errors like:

- DeleteObject: The parameter is invalid
- DeleteObject: There's not enough memory [....]
- DeleteObject: Unknown Win 32 error

I belive that my skinning components are unable to free that memory. And
since windows does that for them when the application is closed, nobody
noticed this leak at the first sight.

"Jonathan Arnold" <jdarnold@buddydog.org> wrote:
> David Scheffel wrote:
>
> > I found quite a few errors in MemProof that are not freed after my
> > application is closed. That's what MemProof says. So do I have to free
these
> > errors that are stored in the WinAPI, or is this a bug in MemProof?
>
> Win32 is very forgiving in that regard. When you program ends, all
> resources and memory are freed up for you. Two concerns:
>
> 1] If it is some memory that is constantly being allocated and not
> freed, your program can use up all available physical memory and
> start paging off to the hard disk - bad.
>
> 2] If your program some day turns into a DLL, that memory won't be
> freed until the calling program exits, not just when the DLL exits.
>
> So if you allocate some memory on startup and then never re-allocate, and
> don't free it, you are probably pretty safe. But there still shouldn't
> be any reason for your app to not free up any resources or memory it
> uses. There are some memory leaks in the VCL & RTL, but there's not
> much you can do about that.
>
> -- 
> Jonathan Arnold         C/C++/CBuilder Keen Advice:
> http://www.keen.com/categories/categorylist_expand.asp?sid=5156620
>     Comprehensive C++Builder link site:
> http://www.buddydog.org/C++Builder/c++builder.html