[
https://issues.apache.org/jira/browse/PDFBOX-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532396#comment-17532396
]
Tilman Hausherr commented on PDFBOX-5143:
-----------------------------------------
{noformat}
java.util.ConcurrentModificationException
at java.util.ArrayList.forEach(ArrayList.java:1262)
at
org.apache.fontbox.cff.Type1CharString.handleSequence(Type1CharString.java:168)
at
org.apache.fontbox.cff.Type1CharString.render(Type1CharString.java:157)
at
org.apache.fontbox.cff.Type1CharString.getPath(Type1CharString.java:134)
at org.apache.fontbox.cff.CFFType1Font.getPath(CFFType1Font.java:65)
at
org.apache.pdfbox.pdmodel.font.PDType1CFont.getPath(PDType1CFont.java:178)
{noformat}
this happens if the {{type1Sequence}} list is modified within {{foreach}}.
Which can happen in Type2CharString.addCommand(). But I wonder why this never
made problems in the deleted {{CharStringHandler.handleSequence()}} ?!
> Refactor/Simplify CFF parsing
> -----------------------------
>
> Key: PDFBOX-5143
> URL: https://issues.apache.org/jira/browse/PDFBOX-5143
> Project: PDFBox
> Issue Type: Improvement
> Components: FontBox
> Affects Versions: 3.0.0 PDFBox
> Reporter: Andreas Lehmkühler
> Assignee: Andreas Lehmkühler
> Priority: Major
> Fix For: 3.0.0 PDFBox
>
> Attachments: evince-bug431088.pdf
>
>
> The classes used for the parsing of CFF-based fonts have some room for
> improvements w.r.t. the memory footprint, the complexity of the code and the
> test coverage.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
