<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 100% CPU Utilization Problem</title>
	<atom:link href="http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/</link>
	<description>This is the official blog of Adobe (Acrobat) Reader for Unix Platforms. It attempts to bring the developers of Adobe Reader for Unix closer to the users. Stay tuned to this space for developer stories, release announcements, user experiences and more!</description>
	<lastBuildDate>Fri, 15 May 2009 02:22:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Proxy User</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-586</link>
		<dc:creator>Proxy User</dc:creator>
		<pubDate>Wed, 21 Jan 2009 23:23:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-586</guid>
		<description><![CDATA[The solution worked for me as well. I&#039;m using Fedora 7 with Acroread 8.1.3. Without setting the proxy, Acroread would utilize 100% of the CPU... which is what lead me to this web page. I am behind a corporate firewall and proxy, so once I manually set the proxy and restarted Acroread, my processor utilization was back to normal. Thanks!
]]></description>
		<content:encoded><![CDATA[<p>The solution worked for me as well. I&#8217;m using Fedora 7 with Acroread 8.1.3. Without setting the proxy, Acroread would utilize 100% of the CPU&#8230; which is what lead me to this web page. I am behind a corporate firewall and proxy, so once I manually set the proxy and restarted Acroread, my processor utilization was back to normal. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aron</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-585</link>
		<dc:creator>Aron</dc:creator>
		<pubDate>Mon, 12 Jan 2009 03:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-585</guid>
		<description><![CDATA[I got some news Everyone!

The system is still Debian &quot;lenny&quot; on AMD Turion X2 notebook, linux-kernel 2.6.28.

I installed the compiz, and after I started it, the 100% CPU utilization problem came back!

After I uninstalled compiz, the problem disappeared again!

:-)
]]></description>
		<content:encoded><![CDATA[<p>I got some news Everyone!</p>
<p>The system is still Debian &#8220;lenny&#8221; on AMD Turion X2 notebook, linux-kernel 2.6.28.</p>
<p>I installed the compiz, and after I started it, the 100% CPU utilization problem came back!</p>
<p>After I uninstalled compiz, the problem disappeared again!<br />
 <img src='http://blogs.adobe.com/acroread/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aron</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-584</link>
		<dc:creator>Aron</dc:creator>
		<pubDate>Sun, 11 Jan 2009 15:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-584</guid>
		<description><![CDATA[Hi!

I also had this problem, but now it seems to get solved :-)

My config:
Amd turion x2 notebook (fujitsu-siemens).
OS: Debian testing release (lenny), 32 bit.
I installed the reader from the deb package.

Im not sure, that it was the thing that solved, but after the kernel upgrade from 2.6.26-1 to 2.6.28 I installed the reader again, and now it works well as standalone, and also in iceweasel/firefox (i had to compile the kernel from source).

There was also another change in the environment, I installed the latest official Nvidia Geforce driver on my notebook. Before that I was using the free driver shipped with Debian.

I hope this helps You too!
Bye!
]]></description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>I also had this problem, but now it seems to get solved <img src='http://blogs.adobe.com/acroread/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>My config:<br />
Amd turion x2 notebook (fujitsu-siemens).<br />
OS: Debian testing release (lenny), 32 bit.<br />
I installed the reader from the deb package.</p>
<p>Im not sure, that it was the thing that solved, but after the kernel upgrade from 2.6.26-1 to 2.6.28 I installed the reader again, and now it works well as standalone, and also in iceweasel/firefox (i had to compile the kernel from source).</p>
<p>There was also another change in the environment, I installed the latest official Nvidia Geforce driver on my notebook. Before that I was using the free driver shipped with Debian.</p>
<p>I hope this helps You too!<br />
Bye!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-583</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Wed, 07 Jan 2009 23:53:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-583</guid>
		<description><![CDATA[The correct proxy settings fix the bug for me too.
What to say else that I&#039;m not impressed by adobe developpers...
A simple googling shows that everybody seem to have the bug, except adobe: &quot;unfortunately we are unable to replicate this issue locally&quot;

]]></description>
		<content:encoded><![CDATA[<p>The correct proxy settings fix the bug for me too.<br />
What to say else that I&#8217;m not impressed by adobe developpers&#8230;<br />
A simple googling shows that everybody seem to have the bug, except adobe: &#8220;unfortunately we are unable to replicate this issue locally&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aspen Olmsted</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-582</link>
		<dc:creator>Aspen Olmsted</dc:creator>
		<pubDate>Wed, 03 Dec 2008 07:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-582</guid>
		<description><![CDATA[I can reproduce the problem every time on any machine running centos 5.2.

The problem happens if you open a pdf from inside firefox.  When you close the tab with the pdf in it the cpu will spike.

I tried this with Opera instead of firefox and the problem does not happen
]]></description>
		<content:encoded><![CDATA[<p>I can reproduce the problem every time on any machine running centos 5.2.</p>
<p>The problem happens if you open a pdf from inside firefox.  When you close the tab with the pdf in it the cpu will spike.</p>
<p>I tried this with Opera instead of firefox and the problem does not happen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massimiliano</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-581</link>
		<dc:creator>Massimiliano</dc:creator>
		<pubDate>Thu, 27 Nov 2008 15:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-581</guid>
		<description><![CDATA[The same for me, on Ubuntu blabla...
Sounds like a memory leak in the application.
]]></description>
		<content:encoded><![CDATA[<p>The same for me, on Ubuntu blabla&#8230;<br />
Sounds like a memory leak in the application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Campbell</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-580</link>
		<dc:creator>Paul Campbell</dc:creator>
		<pubDate>Tue, 07 Oct 2008 04:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-580</guid>
		<description><![CDATA[RedHat Enterprise 5.2
Dell Precision 360 - dual processor
acroread-8.1.2.SU1-2.el5
acroread-plugin-8.1.2.SU1-2.el5

]]></description>
		<content:encoded><![CDATA[<p>RedHat Enterprise 5.2<br />
Dell Precision 360 &#8211; dual processor<br />
acroread-8.1.2.SU1-2.el5<br />
acroread-plugin-8.1.2.SU1-2.el5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Holler</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-579</link>
		<dc:creator>Jan Holler</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-579</guid>
		<description><![CDATA[The Problem still exists. Even on Fedora 9 and Centos 5.2 (core2duo, 2,4MHz, 3GB RAM). I cannot understand why Adobe is not able to solve this problem. Have a look at the output of &quot;top&quot; (rearranged for the forum):

AdobeReader_deu-8.1.2_SU1-1

PID  VIRT  %CPU  %MEM
4088 797m    56  21.9

TIME    COMMAND
7:26.09 acroread

3425 135m    44  2.4
9:20.05 X

]]></description>
		<content:encoded><![CDATA[<p>The Problem still exists. Even on Fedora 9 and Centos 5.2 (core2duo, 2,4MHz, 3GB RAM). I cannot understand why Adobe is not able to solve this problem. Have a look at the output of &#8220;top&#8221; (rearranged for the forum):</p>
<p>AdobeReader_deu-8.1.2_SU1-1</p>
<p>PID  VIRT  %CPU  %MEM<br />
4088 797m    56  21.9</p>
<p>TIME    COMMAND<br />
7:26.09 acroread</p>
<p>3425 135m    44  2.4<br />
9:20.05 X</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tuatha</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-578</link>
		<dc:creator>Tuatha</dc:creator>
		<pubDate>Mon, 22 Sep 2008 16:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-578</guid>
		<description><![CDATA[Hi,

In the Windows version you can disable the auto-update feature, but I can&#039;t find the same option in the Linux version. Am I missing this or it is not there?

Thanks,
Tuatha
]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>In the Windows version you can disable the auto-update feature, but I can&#8217;t find the same option in the Linux version. Am I missing this or it is not there?</p>
<p>Thanks,<br />
Tuatha</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan L Johnson</title>
		<link>http://blogs.adobe.com/acroread/2008/04/09/100_cpu_utilization_problem/#comment-577</link>
		<dc:creator>Ryan L Johnson</dc:creator>
		<pubDate>Sat, 23 Aug 2008 05:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/acroreaddev/2008/04/09/100_cpu_utilization_problem/#comment-577</guid>
		<description><![CDATA[openSuSE 10.3 KDE
acroread-8.1.2_SU1-0.1
firefox 3.0.1-2.1
xorg-x11-7.2-135.5


yeah this is getting really annoying.  I don&#039;t see this happen if I view the pdf with regular adobe acrobat reader (only happens when I view in firefox).

It doesn&#039;t always happen immediately (but can).

If I close the web page (window or tab) it doesn&#039;t end the &#039;acroread&#039; PID).  I have to kill it.  Sometimes it won&#039;t start &quot;hogging&quot; the CPU for a few hours after the process has been running, or even after the window/browser has been closed.
]]></description>
		<content:encoded><![CDATA[<p>openSuSE 10.3 KDE<br />
acroread-8.1.2_SU1-0.1<br />
firefox 3.0.1-2.1<br />
xorg-x11-7.2-135.5</p>
<p>yeah this is getting really annoying.  I don&#8217;t see this happen if I view the pdf with regular adobe acrobat reader (only happens when I view in firefox).</p>
<p>It doesn&#8217;t always happen immediately (but can).</p>
<p>If I close the web page (window or tab) it doesn&#8217;t end the &#8216;acroread&#8217; PID).  I have to kill it.  Sometimes it won&#8217;t start &#8220;hogging&#8221; the CPU for a few hours after the process has been running, or even after the window/browser has been closed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
