Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure that the /Properties, used with optional content, is actually loaded *before* parsing the operatorList/textContent (PR 12095 follow-up) #13275

Merged
merged 1 commit into from
Apr 20, 2021
Merged

Ensure that the /Properties, used with optional content, is actually loaded *before* parsing the operatorList/textContent (PR 12095 follow-up) #13275

merged 1 commit into from
Apr 20, 2021

Commits on Apr 20, 2021

  1. Ensure that the /Properties, used with optional content, is actually … 

    …loaded *before* parsing the operatorList/textContent (PR 12095 follow-up)

By not waiting for the /Properties to load, before parsing of the operatorList/textContent starts, there's a very real risk that a `MissingDataException` will be thrown when trying to access the data in the `PartialEvaluator.parseMarkedContentProps` method.
If this ever happens it will thus lead to incomplete and/or outright broken rendering, and with e.g. `disableAutoFetch=true` set the likelihood of this occuring would increase quite a bit.

*Please note:* While I've not yet seen this error in an actual PDF document, it can happen during loading if you're unlucky enough with e.g. the structure of the PDF document and/or the download speed offered by the server.
    @Snuffleupagus
    Snuffleupagus committed Apr 20, 2021
    Configuration menu
    Copy the full SHA
    8f6543c View commit details
    Browse the repository at this point in the history