AccessViolationException was unhandled

[bgbnbigben]

Hi,

It seems the PXCp_ReadDocumentW is slightly buggy and throws an AccessViolationException when reading the PDF available at http://www.cs.huji.ac.il/~feit/papers/FB13IC.pdf. I've attached a MWE to this post, too -- is there something obvious I'm doing wrong, or failing that will this bug be fixed?

Regards,
- Ben

[Stefan - PDF-XChange]

Hi Ben,

Testing your file with the PXCProDemo from the PDF Tools SDK Examples folder works for me and I don't get any error messages, so can you please make sure you have the latest Tools SDK build and then test with some of the samples we have prepared.

Regards,
Stefan

[bgbnbigben]

Hi Stefan,

Yes, you're right -- with the provided demos, it seems to work fine. Unfortunately, the demos compile with .NET 2.0, whereas my sample project compiles with .NET 4.5 (though it's equally broken in .NET 4.0). Could you, please, confirm for me that it works for you under 4.x?

Regards,
- Ben

[Stefan - PDF-XChange]

Hi Ben,

Checking that with one of my colleagues from the dev team now.

Regards,
Stefan

[Stefan - PDF-XChange]

Hello again bgbnbigben,

We've just tested - and our sample projects compile fine with .NET 4.5, also it appears like your archive is broken.

Regards,
Stefan

[bgbnbigben]

Hi Stefan,

Thanks for your work following this up.

The archive opens fine for me -- it was constructed on Windows 8 using 7zip, but it opens under Windows 7 with winrar, so *shrugs*. I'll recreate and reattach it, using the default zip tool bundled with Windows 8.
The sample projects also compile fine for me, however the don't execute under my Windows 8 virtual machine (specifically with the text extraction demo, the Windows form tool seems to hang and then be forcibly terminated by the OS), so it seems like there might be some strange toolchain issue. My windows 8 vm is relatively fresh and untouched aside from VS2012. Could you ask the dev team what their compilation tools are?

Regards,
Ben

[bgbnbigben]

Hi Stefan,

It's almost unequivocally a VS bug; if I disable "Enable the Visual Studio debugging process" it works perfectly. Sorry for the hassle!

- Ben

[Stefan - PDF-XChange]

Hi Ben,

Glad that you found the villain! Let us know if we can help further!

Regards,
Stefan