[
https://issues.apache.org/jira/browse/PDFBOX-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393619#comment-13393619
]
Andreas Lehmkühler commented on PDFBOX-1099:
--------------------------------------------
Unfortunately the test issue was "overwritten" by the jenkins issue. You can
see the yellow bubble at the overview of build #493 [1] which indicates a test
issue. At least the result of build #494 [2] makes it clear.
P.S.: I've tried to start a new build manually, but it didn't work due to a svn
issue. Mayby a maintenance issue, as the infra peeps announced to switch svn to
read-only to import some data.
[1] https://builds.apache.org/job/PDFBox-trunk/493/
[2] https://builds.apache.org/job/PDFBox-trunk/494/
> Only parsing object streams if they are referenced by the xref table / stream
> -----------------------------------------------------------------------------
>
> Key: PDFBOX-1099
> URL: https://issues.apache.org/jira/browse/PDFBOX-1099
> Project: PDFBox
> Issue Type: Improvement
> Components: Parsing
> Reporter: Thomas Chojecki
> Assignee: Timo Boehme
> Fix For: 1.8.0
>
> Attachments: 2012-06-13_COSDocument_xrefObjStream.patch,
> img1600315916950176362.pdf
>
>
> Some pdf documents have objects streams and don't reference them through the
> xref table / stream. To prevent the stream parser to dereference such object
> streams, we need to implement the type 2 part (case 2) inside the
> PDFXRefStreamParser and store the objects inside a map. This will take some
> load from the stream parser (see PDFBOX-1098) and causes less failures while
> parsing a document.
> A sample pdf can be get from the issue PDFBOX-1098 and a patch is coming
> soon.
--
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