[
https://issues.apache.org/jira/browse/PDFBOX-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16700645#comment-16700645
]
Tilman Hausherr commented on PDFBOX-4384:
-----------------------------------------
This is now a different strategy, the page tree validation process is aborted.
It is still possible that other errors appear after that. It is also possible
that it doesn't abort because there is a super-complicated page. This is too
difficult to change.
To configure, call {{document.getContext().getConfig().setMaxErrors(xxx)}}.
> PDF/A Document Validation out of memory
> ---------------------------------------
>
> Key: PDFBOX-4384
> URL: https://issues.apache.org/jira/browse/PDFBOX-4384
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Affects Versions: 2.0.8, 2.0.12
> Reporter: Vincenzo Mangiapanello
> Priority: Major
>
> Hi everyone,
> validating a customer PDF file, using
> {code:java}
> document.validate(){code}
> we recognise that if the file itself has an enormous numbers of validation
> errors, the process goes to OutOfMemory and at the end the we get the GC
> error.
> In our case the file has more than 550.000 errors. So we cannot go head with
> the conversion to PDF/A.
> To avoid this kind of error it could be useful to configure a max number of
> validation errors to stop the process if this value has been reached.
> We cannot attach the original document, because it is a customer's file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
