Red Hat Bugzilla – Bug 443311
Adabe Acrobat Reader fills up available memory
Last modified: 2008-07-25 19:01:02 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.8.1.13) Gecko/20080325 Fedora/2.0.0.13-1.fc8 Firefox/2.0.0.13 Description of problem: When using Adobe Acrobat Reader in Firefox 2.0.x, upon closing either the document tab or closing Firefox, acroread does not terminate, but simply keeps on running and slowly increases its memory size until all available memory (RAM and swap) is filled. When the system completely runs out of memory, the USB keyboard becomes unresponsive (Gnome & KDE), and only the mouse pointer moves but does not accept clicks. The memory issue was discovered by leaving the system monitor running and keeping track of the memory usage. Upon close monitoring acroread reached 1.2GB of memory before I killed the process. Also, when opening a new Firefox instance and opening a PDF document, a new instance of acroread is started instead of using the active process. Version-Release number of selected component (if applicable): 8.1.2 How reproducible: Always Steps to Reproduce: 1. Open PDF document in Firefox. 2. Close Firefox. 3. Check system monitor for acroread process. Actual Results: Acroread process increases in memory size with no open windows. Expected Results: Acroread process should have terminated upon closing Firefox. Memory usage should decrease of remain static. Additional info: Acrobat Reader 8.1.2 - Installed from Adobe site.
I am really sorry, but I don't see here any issue with the software we provide. I can offer only two suggegstions: a) if you can use evince (or okular, if you are on KDE) -- they are fairly good PDF viewers and tedn to be much more stable than Adobe Acrobat Reader. b) if you have to use Adobe Acrobat Reader, you can try to install nspluginwrapper, run mozilla-plugin-config -f -c and mozilla-plugin-config -l, that acrobat reader has been succesfully wrapper, and then run firefox. Adobe Acrobat could still malfunction (we cannot really change anything about that), but being in the stricter confinment, Firefox should not be harmed. Closing as NOTABUG