From zombie_ryushu at yahoo.com Fri Aug 22 02:58:34 2014 From: zombie_ryushu at yahoo.com (Zombie Ryushu) Date: Thu, 21 Aug 2014 22:58:34 -0400 Subject: Serious Bug Adobe Acrobat 9.5.5 100% CPU Usage. Help! Message-ID: <53F6B1DA.9060206@yahoo.com> I have a vexing and severe situation on my hands dealing with the Adobe Acrobat Reader. I recently migrated my systems from Mageia 3 to Mageia 4. The change in glib and gtk-pixbuf has created some sort of CPU spiking condition in certain instances when an Adobe PDF with FireFox. Before I go into a huge amount of detail. I want to lay down the following: Due to the nature of my employment, and the technical requirements of the tasks I preform using Adobe Reader for Linux, no alternative PDF Readers will be entertained The requirements of this application are that forms be filled out online and submitted to a website using the Oracle JRE and Adobe Acrobat Reader via the NPAPI Plugin. None of the Alternative readers have this online submission capability. Evince is close, but it's NPAPI Plugin is not packaged and in a very Alpha state. This did work under Mageia 2 and 3. With that out of the way. Under Mageia 4, there exists a situation where the Acrobat Reader can freeze the Browser tab. This is seemingly random, and unpredictable, and can be affected by exactly what PDF you open. When this happens, acroread spikes the CPU to 100% and the browser must be closed, and sometimes the acroread process terminated by a kill -9 When running acroread stand alone, Acroread displays the following errors extremely commonly. I've run Stack trace and I can't figure out why Acroread is trying to address 64 bit libraries, but acroread still runs and appears to function normally as a stand alone application. Another user with both Mageia and Fedora systems have tested and reproduced the problem, but exclusively on Mageia (and Rosa), Fedora seems not to be affected. The systems I use are all 64 bit and I know this is a 32 bit application. Some 32 bit gdk-pixbuf libraries cannot be installed concurrently with 64 bit counterparts. So what I would like is someone's assistance with getting Acrobat reader to a functioning state again. This should be considered priority. I tried disabling the NPAPI Plugin, and just using Acroread directly. Its as I feared, the PDF is submitting information back via https to a CGI, without the NPAPI layer, the PDF can't communicate with the Javascripting via CGI, and thus, can't save the Document. The document opens, but you cannot save it back to the CGI. So the problem has to be in nspluginwrapper. -------------- next part -------------- An HTML attachment was scrubbed... URL: