[
https://issues.apache.org/jira/browse/PDFBOX-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398118#comment-17398118
]
Andreas Lehmkühler commented on PDFBOX-5214:
--------------------------------------------
It isn't related to the logging and has nothing to do with TestPDFToImage. In
my case the fonts of the
[pdf|https://issues.apache.org/jira/secure/attachment/12816016/Signed-Document-2.pdf]
from PDFBOX-3396 are replaced after flattening. That leads to different
rendering results.
After some debugging I've found the reason. The static instances of the 14
standard fonts within PDType1Font aren't threadsafe. Those fonts are backed by
a COSDictionary which isn't supposed to be stable.
> File generated differently depending on test call
> -------------------------------------------------
>
> Key: PDFBOX-5214
> URL: https://issues.apache.org/jira/browse/PDFBOX-5214
> Project: PDFBox
> Issue Type: Bug
> Components: Writing
> Affects Versions: 3.0.0 PDFBox
> Reporter: Tilman Hausherr
> Assignee: Andreas Lehmkühler
> Priority: Major
> Fix For: 3.0.0 PDFBox
>
> Attachments: EmptySignatureForm_FullPackageTest.pdf,
> EmptySignatureForm_SingleClassTest.pdf
>
>
> Something weird is happening in {{TestCreateSignature.testPDFBox3978}}. The
> file {{EmptySignatureForm.pdf}} that is generated has different object
> streams depending on whether it is generated within a full test of the
> examples package, or if the {{TestCreateSignature}} class is tested. The two
> files should be identical except for the ID.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
