I recognised some problems using the combination app-text/acroread-8.1.2 and www-client/mozilla-firefox-2.0.0.12 When I open a pdf inside firefox and close the tab showing the pdf or go back in the history the pdf view is closed. But there is still a ld-linux.so.2 process running with about 50% of CPU usage. Furthermore X is consuming the other 50%. The ld-linux process is continuing to use more and more memory which leads at the end to a hanging system. A cat on the ld-linux processes /proc/.../cmdline gives /lib/ld-linux.so.2/opt/Adobe/Reader8/Reader/intellinux/bin/acroread--display:0.0-progressPipe3-exitPipe4 Reproducible: Always Steps to Reproduce: 1. Open a pdf by visiting a link in firefox 2. Close the tab or go back in history Actual Results: A ld-linux.so.2 process is using 50% of CPU and is continuesly consuming more and more memory Additional X is using the remaining 50% of the CPU. Expected Results: Finish all processes related to the acroread plugin. The problem doesn't occure using app-text/acroread-7.0.9-r1. The remaining ld-linux.so.2 process can only be killed using the KILL signal!
1/ This has zero in common with Gentoo Bugzilla product. 2/ We obviously cannot fix anything in Adobe Reader...
(In reply to comment #1) > 1/ This has zero in common with Gentoo Bugzilla product. > 2/ We obviously cannot fix anything in Adobe Reader... > The problem seems to be in acrobat 8.1.2: http://blogs.adobe.com/acroread/2008/02/known_issues_with_adobe_reader.html#comments For some people disabling "Allow Fast Web View" could help as mentioned in the above link.
*** Bug 213675 has been marked as a duplicate of this bug. ***
*** Bug 214123 has been marked as a duplicate of this bug. ***
As noted above, there's nothing we could here -> marking UPSTREAM. http://blogs.adobe.com/acroread/2007/09/known_issues_with_adobe_reader_1.html
*** Bug 230565 has been marked as a duplicate of this bug. ***
*** Bug 214302 has been marked as a duplicate of this bug. ***
The problem still exists with Acroread 8.1.3 and Firefox 3.0.5 on x86_64. Looking at the referenced Adobe page, this is mentioned in the user comments, but I don't see it as an officially recognized bug.
