[ 
https://issues.apache.org/jira/browse/PDFBOX-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515095#comment-17515095
 ] 

Andreas Lehmkühler commented on PDFBOX-5400:
--------------------------------------------

{quote}Found the difference between trunk and 2.0.{quote}
There are a lot of changes in the trunk so that it isn't that easy to compare 
both to each other

{quote}In both branches, if a referenced object is missing in the xref table, 
the object should be read from a brute force object list.{quote}
Correct, in 2.0 it was triggered in {{checkXrefOffsets}}, but due to the 
changes from PDFBOX-5238 it isn't any more in every case. The following code 
still assumes that the bf search was triggered in {{checkXrefOffsets}} if 
necessary.

However, it is a valid hint and may lead to a solution. My first attempt to 
trigger a later bf search didn't work, the exception is gone but the rendering 
is empty. I'll have to dig deeper


> Page tree root must be a dictionary
> -----------------------------------
>
>                 Key: PDFBOX-5400
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5400
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Parsing
>    Affects Versions: 2.0.26
>            Reporter: Tilman Hausherr
>            Assignee: Andreas Lehmkühler
>            Priority: Major
>              Labels: regression
>         Attachments: 4ECBGZDM5GUZG7UT75RV5GTUFWF5TSXK.pdf
>
>
> worked in 2.0.25
> {noformat}
> Caused by: java.io.IOException: Page tree root must be a dictionary
>     org.apache.pdfbox.pdfparser.PDFParser.initialParse(PDFParser.java:198)
>     org.apache.pdfbox.pdfparser.PDFParser.parse(PDFParser.java:226)
>     org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:1107)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to