100% CPU Utilization Problem
Some of our users have reported a 100% CPU utilization problem while using Adobe Reader 8.x for Unix platforms. This has been discussed on the user-to-user forums post but unfortunately we are unable to replicate this issue locally. Some of the users have reported that this problem seems to go away if you set the proxy in Preferences->Internet to "Manual Proxy Configuration" and enter the proxy server and associated port #, then exit Acroread and restart.
I would request all those users who have faced this issue to post comments on how they reproduced the problem and give some information on their OS/distribution, etc. to help us isolate the issue. Thanks for your continuous feedback and comments!
Comments
I had this issue on a 2-core machine. Starting one Acrobat (in Firefox) would hog one core 100%. Starting another instance would hog the other to 100%. This is on SuSE Linux Enterprise 10.1.
I tried the proxy fix and it worked. I'm behind a corporate intranet so the proxy is a plausible cause for this (how I don't know, that's your task now, Adobe).
Thanks for the tip!
Posted by: Adam Lindberg | April 9, 2008 01:24 PM
I can replicate this issue quite easily when using Reader as a Firefox plugin, just by surfing to random PDF files on the Internet. Sometimes the problem manifests and sometimes it does not. CPU usage stays constantly high on one core (though not 100%) and memory use increases until the acroread process is killed.
I have a Direct connection (no proxy) configured.
System details:
Fedora 8, Quad-Core
Kernel 2.6.24.4-64.fc8
Firefox 2.0.0.13 x86_64
Adobe Reader 8.1.2 rpm
nspluginwrapper 0.9.91.5
Cheers,
Raman
Posted by: Raman Gupta | April 11, 2008 07:21 AM
You need look at the acrobat code that is trying to access pmupsw.adobe.com. Acroread gets into an infinite loop when it can't access this site. I ran wireshark and it chokes right after requesting this site ip from dns.
Posted by: anonymous | April 11, 2008 08:46 PM
sorry for cross commenting, i found this after posting comment to "Known Issues with Reader 8.1.2" i think this is correct place.
We have this issues 100% CPU usage and up to 200MB memory usage for 100Kb pdf dokument:
on Windows Systems with AR8.1.2
We have some converted pdf dokuments (from eps), which causes a high cpu usage on Windows XP/Vista systems. Same dokument causes AR8.1.2 crashes on other Windows XP Systems. Same documents can be opened with AR7.x
We found that this issue comes while using Adobe Distiller 7.0.9 or ghostscript (with multiple devices setting) but not with Adobe Distiller 8.1
Can you please point out the changes/issues from Distiller 7.0.9 to 8.1 an Reader 7.x to 8.x
thanks in advance
RL
Posted by: RL | April 17, 2008 03:10 AM
I have the same problem here on two machines, both fedora 8 on core 2 duos (e6600, 7100). I have to kill it using signal 9 to get rid of it. I managed to reproduce it also on centos 5.1 (redhat enterprise 5.1). Acroread is started as a firefox plugin and stays in the process list even after finishing firefox. It is really annoying and I am close to remove acroread if this problem is not getting fixed soon. I do not see why Adobe cannot reproduce the problem. Get a maschine up and running (use xen or kvm for testing if you bother setting up a system freshly) on fedora 8, install firefox and your acroread by yum. That is done in less than 15 minutes.
Posted by: Jan Holler | April 30, 2008 06:52 PM