Rarely crash on some PDF about pikepdf HOT 3 CLOSED

The error indicates that:

1. the file was damaged
2. libqpdf tried to recover the damaged file, but gave up/exhausted its recovery tools

In my experience this usually happens when a file is truncated. Sometimes you can do manual forensic recovery and extract some content, but it all depends how the original was structured.

You should get an exception and that's expected behavior. If you got a crash, meaning the Python interpreter aborted with a segfault or some other error, I'd like to look at the files.

from pikepdf.

Yeh, this is why I closed the issue ...... the documents were extremely damaged..... However, i used a try\catch to skip those docs.

The attachments contain 4 samples.
documents.zip

from pikepdf.

All 4 of these files appear to be truncated. At a glance the first few pages of text/images might be recoverable from the first two, but that's definitely in the realm of forensic data recovery, not what we're trying to do here.

Thanks for your submission.

from pikepdf.