In addition to everything else that's been said/suggested, can I suggest you use leak checking memory manager, e.g. FastMM or MemCheck (See http://v.mahon.free.fr/pro/freeware/memcheck/)
It also includes double free checking which is often the cause of access violations on applcation shutdown (e.g. some object/component has already been freed manually but the VCL holds a stale reference and then tries to also free the pointer. Can happen when you create a component and pass a VCL component as owner and then you also free the component yourself, leaving the VCL trying to free something which doesn't exist.) Walter 2009/3/16 Bembi Prima <[email protected]> > I am really confused on that error message. It keeps showing when I > close > the program.When I try running it without the compiler, the app is still > running in task manager consuming around 50% cpu usage even though I have > already close it. I have to end the process with force. > I have already checked the source, I think I have freed everything, I even > use caFree as the Close Action on OnFormClose event. I also already close > any opened file stream on the app. > I don't know what else trigger that error message. Anyone here have any > knowledge of anything else might trigger that error? > > Thanks. > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed]
