Acrord32.exe started by Explorer won't terminate

Whenever Adobe Reader 6.0 is opened by Explorer's web browser, Acroread32.exe is started, using about 30 megs of ram (Windows 2000).

It doesn't terminate when Explorer does, only at a user log-off.

Is there a way around this, so I don't have to keep going to Task Manager to free up the ram?
gt40mk2Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Karl Heinz KremerCommented:
I think this is intentional: Acrobat stays around because you may view more web pages with PDF documents. The problem is that Explorer does not know if you've used Acrobat for anything else (e.g. open a PDF file on your disk). Acrobat is only loaded once, and every PDF file that you load gets loaded into this one running instance of Acrobat. So if Explorer would kill Acrobat when it exits, you would potentially lose all the PDF's that you've locally opened in Acrobat in this same session.

Even though I always said "Acrobat", the same applies to the Adobe Reader (or Acrobat Reader if you have an older version).

Because the application is not really running , chances are that it does not actually use memory, but gets written out to the page file. So if you make your page file 30MB larger, you should not see a difference how much memory is available (compared to before the change).

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
CSharpeCommented:
This misses the point.

The point is, when Acrod32.exe is in the task list, following reading a PDF file, even though you have closed out of all PDF documents, the next attempt to open a PDF file hangs untill you kill the acrord32.exe that is still in the Task List.

How do you either configure Acrord32.exe to terminate when the last document is closed or confuigure Windows to properly re-connect the running executable without hanging?
Karl Heinz KremerCommented:
Nothing in this question missed the point: The original question was about whey the process hangs around. Your problem is not the problem that was discussed in this question. The process does usually work (it does not look like the question author has this particular problem, and neither do I experience it).

Please open a new question specific to your problem.
cchtukaCommented:
You can avoid this by making Acrobat not open the PDF in the browser...
It's a setting in the Prefs of Acrobat Reader...
gt40mk2Author Commented:

That certainly works. Thanks!

(Sorry I already accepted another answer a long time ago.)


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
Adobe Acrobat

From novice to tech pro — start learning today.