jojothehobo
Tue Oct 29, 2013 8:22:03 pm
Hi All:
i have Adobe Acrobat Reader on my Zorin Ultimate 6 desktop. It has an AMD quad core processor and 8 GB of RAM. It runs well. Today I was using the program "System Monitor" that comes with Gnome to review my disk usage and how my system is using resources.
What I found was that "accroread" was using 100% of one core, even though it wasn't open and I wasn't reading any .pdf documents. I changed the priority (right click on process) from low to very low and then the usage went down to 96%. So I decided to stop the process (not end or kill it). It stopped and then the CPU usage went to zero. So far so good. I then opened up a .pdf document and that went well. The cpu usage (an average number) stayed at zero after the document was opened. It didn't seem to take much longer with the process stopped than with it running.
So my questions are:
1 whether I should leave "accroread" stopped permanently?
2.why it took up a full 1/4 of my processing power?
This is more in terms of understanding, since it isn't giving me a problem (except perhaps less system robustness and ability to handle multiple tasks). Accroread is the only process that does this. I have other options for opening .pdf documents such as evince document reader and pdfsam and master pdf editor. Evince seems to be the only one purely for reading.
3. Does the group think it would be a smart idea to get rid of Adobe Reader all together?
4. What are the recommended replacement options?
Thanks , Jojo
i have Adobe Acrobat Reader on my Zorin Ultimate 6 desktop. It has an AMD quad core processor and 8 GB of RAM. It runs well. Today I was using the program "System Monitor" that comes with Gnome to review my disk usage and how my system is using resources.
What I found was that "accroread" was using 100% of one core, even though it wasn't open and I wasn't reading any .pdf documents. I changed the priority (right click on process) from low to very low and then the usage went down to 96%. So I decided to stop the process (not end or kill it). It stopped and then the CPU usage went to zero. So far so good. I then opened up a .pdf document and that went well. The cpu usage (an average number) stayed at zero after the document was opened. It didn't seem to take much longer with the process stopped than with it running.
So my questions are:
1 whether I should leave "accroread" stopped permanently?
2.why it took up a full 1/4 of my processing power?
This is more in terms of understanding, since it isn't giving me a problem (except perhaps less system robustness and ability to handle multiple tasks). Accroread is the only process that does this. I have other options for opening .pdf documents such as evince document reader and pdfsam and master pdf editor. Evince seems to be the only one purely for reading.
3. Does the group think it would be a smart idea to get rid of Adobe Reader all together?
4. What are the recommended replacement options?
Thanks , Jojo