Thread View: adobe.acrobat.unix
4 messages
4 total messages
Started by Hugo_Valadas
Thu, 21 Dec 2006 16:16
Adobe Reader CPU Usage
Author: Hugo_Valadas
Date: Thu, 21 Dec 2006 16:16
Date: Thu, 21 Dec 2006 16:16
13 lines
1521 bytes
1521 bytes
Hello All, The problem i'm having is that "acroread" process after being open for some time (many hours or even days) starts to use all the CPU without anyone touch the application. This causes lots of trouble because i'm using all the time simulation software and "acroread" starts to share CPU with my mission critical applications and I cannot be always checking if acroread has crashed. I've tried with more than one Linux distribution and have read in some web forums that other linux distributions have the same problem. Currently i'm using CentOS 4.4 (Linux 2.6.9-34.0.2.ELsmp #1 SMP Fri Jul 7 19:52:49 CDT 2006 i686 i686 i386 GNU/Linux) Even in CentOS 4.3 , 4.2 , 3.4 they all had the same problem. I'm using acroread 7.0.8 but older versions of 7.x did the same. Please share some ideas about this issue. Thanks
Re: Adobe Reader CPU Usage
Author: AshutoshJSharma
Date: Fri, 22 Dec 2006 10:30
Date: Fri, 22 Dec 2006 10:30
6 lines
692 bytes
692 bytes
Hi Hugo, This is a known issue and we will be working on this for the next release. Thanks, Ashutosh
Re: Adobe Reader CPU Usage
Author: Hugo_Valadas
Date: Fri, 22 Dec 2006 12:27
Date: Fri, 22 Dec 2006 12:27
4 lines
622 bytes
622 bytes
Ok. Thank you. Keep up the good work Best Regards, HV
Re: Adobe Reader CPU Usage
Author: Phil Sherman
Date: Mon, 25 Dec 2006 17:09
Date: Mon, 25 Dec 2006 17:09
25 lines
2421 bytes
2421 bytes
If you have to keep the reader open for long periods of time, you might try the one of the following. They won't correct the problem but should decrease the impact until a fix is generated. A combination of the two may be the best choice. 1. Use "nice" to start acroread. This will lower the dispatching priority of acroread and, when it starts eating the processor, should decrease or eliminate the impact on your critical applications. You can replace acroread with a script that uses "nice" to execute a renamed acroread. 2. Write a script to execute "top" and use it to monitor the cpu usage of the reader. When it starts eating cycles, kill it. This will require you to restart the reader after it has been killed. If you don't want to automatically kill the reader, send the userid running the reader a message that it needs to be restarted. Phil Sherman Hugo_Valadas@adobeforums.com wrote: > Ok. Thank you. Keep up the good work > > Best Regards, > HV
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads