You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Timo Boehme (JIRA)" <ji...@apache.org> on 2012/06/11 18:29:43 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13292864#comment-13292864 ]
Timo Boehme commented on PDFBOX-1336:
-------------------------------------
As you can see from the crash log the error occurs in a native library called by the Java VM. The library is supposed to handle font data. Thus the font library shipped with your OS seems to have a bug or the font data is corrupted and the library cannot cope with it. Thus I don't think there is something we can do at PDFBOX side. If you can share the problematic document we could test if this problem occurs with other environments as well.
> 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
> Priority: Critical
> Attachments: hs_err_pid16603.log
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira