<snip>Thanks for the info. Maybe this will help others, but this is not my problem. My problem is
3. Always associated with use of acroread, and usually after printing from acroread.
Well, that's a horse of a different color. Not to put too fine a point on it, the acroread browser extension <cough>sucks</cough>, and has a strong tendency to crash any browser (Win or Lin).
I don't know much about this so I can't speak "technically", but what I have observed is that using the acroread plugin (meaning actually viewing a PDF document using it via the browser) for an extended period (like a couple of hours, i.e., just leaving the browser open with the plugin in use) will eventually cause a failure in the browser (resource leak?).
Also, unless you actively close the plugin tab, acroread will stay loaded if you close the browser or it crashes, and firefox won't restart until you actually go into a process manager and stop the stupid plugin.
Solutions?
1) download the PDF and use the reader to open it standalone, rather than opening it in a browser window;
2) close the plugin tab *as soon as you finish using it*, do not leave it open for any reason, and definitely do not close the browser with the plugin tab still active.
Hope this helps somewhat,
Holly
-- [email protected] mailing list
