I think I have seen this when I freed a component on a form. When the form was destroyed it tried to free it again.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, March 16, 2009 11:47 AM To: [email protected] Subject: Re: [delphi-en] EAccessViolation, read of address 00000000 Two suggestions: Brute force: step through finalization using the debugger. I have found one or two that way. Memory leaks: google for memcheck. It has saved me once or twice. The program is attempting to use a nil pointer? > 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] > > ------------------------------------ ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [email protected]! Groups Links
