On Thursday 03 January 2008, Leslie Satenstein wrote: > Adobe appears to quit, but a process is left in memory, to churn away. It > is quiet for a while, then begins to consume considerable CPU cycles, and > then returns to quiet. > Can someone collaborate my findings? I can corroborate, with f8 on i386, no compiz. There have a been a few times, particularly where I had seven or eight Acroreader plugins going in Firefox, where exiting with the Firefox red X in the tab would hang other tabs' acroread, and drive CPU way up. While I don't remember this happening a month or so ago (seems related to a recent update, maybe), but it could have been happening unaware to me. -- Lamar Owen Chief Information Officer Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu
