Adobe Reader plugin crashes on IEEE Xplore pdf

[Felipe Castillo]

The adobe reader plugin is working great in every single website I've used it, except for IEEE Xplore. The website is known for handling pdf in a weird way.
Every time I try to access an article (pdf) I see the pdf being loaded, a progress bar, and when it's done I get a crash message and nothing works. I'm uploading the tracelog I got from the crash.
I know that this is going to be a hard bug to replicate if you don't have access to IEEE Xplore. If you have access to a university library or a university network, you'll be able to access IEEE Xplore, and just doing any search an opening any pdf will give you the error.
I can see under plugins on Firefox that the Adobe Acrobat is working and this is what i get:

    File: libpipelight-adobereader.so
    Path: /usr/lib/pipelight/libpipelight-adobereader.so
    Version: Adobe PDF Plug-In For Firefox and Netscape 11.0.06
    State: Enabled
    Adobe PDF Plug-In For Firefox and Netscape 11.0.06

I'm using Ubuntu 13.10 64bit with Firefox 28.0 from the official repositories.
I'm also using Pipelight 0.2.6~ubuntu13.10.1.

[Michael Müller (mqchael)]

Hi,

I didn't had time yet to do a in depth analysis, but i would guess that the crash is related to the richedit warnings which are shown before the crash:

fixme:richedit:ITextDocument_fnRange stub 0x8538a8
fixme:richedit:ITextDocument_fnFreeze stub 0x8538a8
fixme:richedit:ITextDocument_fnRange stub 0x8538a8
fixme:richedit:ITextSelection_fnGetFont not implemented
fixme:richedit:ITextSelection_fnGetFont not implemented
wine: Unhandled page fault on read access to 0x00000000 at address 0x601a8466 (thread 0024), starting debugger...

The function ITextSelection_fnGetFont is supposed to return a pointer to an Interface and it is only a stub in Wine ( http://source.winehq.org/source/dlls/riched20/richole.c#L893 ) and does not set any value for this parameter. If the Adobe Reader tries to dereference the pointer without checking the return value of the function this would result in an invalid read access. I need to verify this theory later, but I fear that there is no easy way to fix this since neither the ITextDocument nor the ITextSelection interface is correctly implemented for the richedit control in Wine.

Michael

[Michael Müller (mqchael)]

Hi,

seems like you have luck. Some GSOC student is currently working on the missing functions: http://www.winehq.org/pipermail/wine-devel/2014-April/103914.html

Maybe the problem will be solved in one of the next wine versions.

Michael

[Felipe Castillo (fcastillo.ec)]

Thanks for the update, I'll be waiting eagerly for the fix.

On Tue, Apr 15, 2014 at 2:09 PM, Michael Müller <email address hidden> wrote:

> Hi,
>
> seems like you have luck. Some GSOC student is currently working on the
> missing functions: http://www.winehq.org/pipermail/wine-
> devel/2014-April/103914.html
>
> Maybe the problem will be solved in one of the next wine versions.
>
> Michael
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1305414
>
> Title:
> Adobe Reader plugin crashes on IEEE Xplore pdf
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pipelight/+bug/1305414/+subscriptions
>

[Michael Müller (mqchael)]

Hi,

can you please retest? We have added patches which solve some of the problems. Adobe reader still crashes for me sometimes if I use the footer bar, but it does no longer crash for me while simply opening a document. Make sure to use a recent wine-compholio version i.e. 1.7.27 (can be verified by using pipelight --system-check).

Michael

[Felipe Castillo (fcastillo.ec)]

I've updated pipelight to the latest version, I have tried using the Adobe Plugin on Firefox for the IEEExplorer website. It's working without a problem. Searching, the sidebar, thumbnails, save and other features are all working.
I'm using Ubuntu 14.04.1 64bit with the latest Firefox and Pipelight 0.2.7.1

[Michael Müller (mqchael)]

Since the problem is solved for you, I will close this bug report as fixed.

Michael