[
https://issues.apache.org/jira/browse/PDFBOX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Lehmkühler resolved PDFBOX-1609.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.8.2
Assignee: Andreas Lehmkühler
PDFBOX-1580 solves this issue too.
> EXCEPTION_ACCESS_VIOLATION with PDF file and image conversion
> -------------------------------------------------------------
>
> Key: PDFBOX-1609
> URL: https://issues.apache.org/jira/browse/PDFBOX-1609
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 1.8.1
> Reporter: Nico Prenzel
> Assignee: Andreas Lehmkühler
> Fix For: 1.8.2
>
> Attachments: hs_err_pid3532.log, pdfbox.apache.pdf
>
>
> Hello,
> I do receive an unhandled exception during image conversion of the attached
> pdf file.
> For image conversion i've used the PDFToImage.java example.
> The pdf file has been created with Foxit PDF-Printer.
> Every generated pdf file will crash the whole JRE, so my whole application
> crashes with the following trace.
> The affected pdf file has been attached.
> The error report file has been attached.
> Hopefully this error can be handled that the JRE won't crash anymore.
> Thanks
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x720c2d77, pid=3532,
> tid=2620
> #
> # JRE version: 7.0_21-b11
> # Java VM: Java HotSpot(TM) Client VM (23.21-b01 mixed mode windows-x86 )
> # Problematic frame:
> # C [t2k.dll+0x12d77]
> #
> # Failed to write core dump. Minidumps are not enabled by default on client
> versions of Windows
> #
> # An error report file with more information is saved as:
> # U:\Eclipse-Workspace\de.vlh.notes.tools\hs_err_pid3532.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira