On Thu, 2008-01-03 at 22:26 -0500, Lamar Owen wrote: > 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. I'm running F8 on 2 separate systems - a desktop and a laptop. The desktop uses the 32-bit version and the laptop has the 64-bit version. Outside of hardware differences forcing this, both systems are otherwise set up pretty much the same. On both systems, I am noticing general "pokiness", if not outright slowness, when manipulating files and folders. It's worse when Desktop Effects is turned on. Several apps seem to be affected, including Adobe Reader, Document Viewer (evince), and VMware Workstation 6.0.2. It's at its worst when any of these applications are actively running - especially VMware Workstation. I tend to agree this is not a problem with Adobe Reader per se, and I also (with prompted memory), recall that this was not the case as recently as 2 or 3 weeks ago. I would also suspect an update to X, Compiz, or Nautilus along the way is the more likely culprit, but I couldn't say that with absolute certainty. It definitely should be looked into. I'm happy to bugzilla, but I'm not sure what I should file this one under since I don't really know where to start looking for the problem. Ideas? Cheers, Chris -- ==================================================== In theory there is no difference between theory and practice. In practice there is. --Yogi Berra
