Frank Cox wrote:
On Sun, 24 Aug 2008 15:25:26 -0400
"Kevin J. Cummings" <cummings@xxxxxxxxxxxxxxxxxx> wrote:
I see this on occasion, but not all the time.
A problem that I've found when allowing acroread to load pdf files into the
Firefox window is that acroread will go wild if you close the tab.
Open a new tab in Firefox. Load a PDF into the Firefox window. Close the
tab. 100% of the time, I see 100% cpu usage until I "killall acroread".
This is on Fedora 8/x86_64 with FF 2, so it may be different or changed/fixed on
F9.
I've been using FF3 on F9. One of the things happened to me recently
was I was looking at a PDF in FF, I left the computer for 2 hours. When
I returned, the acroread plugin had run wild grabbing memory. The OOM
process was running trying to find processes to kill, my 2GB of
swapspace was practically full, and the machine was very sluggish
(thrashing). I got control back after I was finally able to kill FF and
acroread.... I was then able to turn off swap and re-enable it, and I
was still using less than 30% of my 2GB of RAM after that! Yes, I
agree, FF and acroread are memory hungry. BTW, this was with the
acroread (AdobeReader?) tab still open....
--
Kevin J. Cummings
kjchome@xxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232 (http://counter.li.org)
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
