You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Andreas Lehmkühler (JIRA)" <ji...@apache.org> on 2013/08/04 11:51:56 UTC

[jira] [Resolved] (PDFBOX-1336) JVM Crashes on Linux OS + Sun JVM + PDFBox

     [ https://issues.apache.org/jira/browse/PDFBOX-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Lehmkühler resolved PDFBOX-1336.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Andreas Lehmkühler

It looks good after solving PDFBOX-490 and I'm sure there won't be crashes anymore as PDFBox don't rely on the JDK anymore when rendering TTF fonts.
                
> JVM Crashes on Linux OS + Sun JVM + PDFBox
> ------------------------------------------
>
>                 Key: PDFBOX-1336
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1336
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>         Environment: CentOS 5.6
> Sun JVM Java version: 6 update 31
> Tomcat 7.0.26
>            Reporter: Ann Addicks
>            Assignee: Andreas Lehmkühler
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: CrashTest.java, hs_err_pid16603.log, pdfcrowd_1334685364.pdf
>
>
>  A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x796af64d, pid=16603, tid=2021653392
> #
> # JRE version: 6.0_31-b04
> # Java VM: Java HotSpot(TM) Server VM (20.6-b01 mixed mode linux-x86 )
> # Problematic frame:
> # C  [libfontmanager.so+0x1e64d]  imaginary long double+0x7d
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> I can provide the full error, please let me know.

--
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