Access Violations when closing

In two of my Applications (totally seperate apps, different data,
everything) when you hit the close button and application error occurs.


Access violation at 0x4be41a49 read address 0x388b5708
83 3a 00 74 63 e8 39 10 00 00 64 88

This errors occurs in Delphi and at Runtime. The Delphi Find Error does not
find the code like that causes this problem (so possibly it is occuring in
the VCL).

Does anyone have any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you using your own components?
Do you create any objects?
If so you must free them before closing (in the OnDestroy handler)

Give me some more detail and I'll help more.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
of course.
Silly me.
Everything I create I am Destroying (or Free ing, I've tried both).  

One strange thing I have noticed, on a 486 or a slow Pentium the problem does not occur!

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

gdjAuthor Commented:
 Does the error occur on the same line of code every time? If so why not paste it and the surrounding lines up and it may shed some more light.

The error occurs after all of my code has all been processed.
gdjAuthor Commented:
If you have written some thing like:
mainform.destroy or than this might be the problem.
Generally, instead, you should call mainform.Release.
Thanks - but what did I say?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.