-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
For some PDFs an error can cause the process to run out of memory #33
Comments
Update: Apparently I was testing with a pdf that had some kind of internal error, but was visually otherwise fine. The page 55 out of 68 was broken, which then broke one of the dependencies. I tested it with only pages 54-58, to remove the too many pages assumption, and it still broke. As soon as I fixed the pdf with an external tool, it worked. My assumption was a broken/missing font, due to the warnings below (outputted at However, since the warning was firing for ALL the pages, and none up until page 55 broke, I believe the problem lies elsewhere, since the problematic dependency seems to be I am not sure how to fix this or what specifically causes it, however, perhaps some kind of error handling could be added? Warnings:
Errors:
|
@Zirafnik Same issue here |
Please try v3.3.0 |
A PDF with many pages, causes the Node to run out of memory.
This is a similar issue to the one in 'pdf2pic' library: yakovmeister/pdf2image#54It can be solved with manual batching, with arrays of page numbers, but it is not a sexy solution, as you first need to determine the number of pages in the document with an external library (such as 'pdfjs-dist') and then create the arrays, allowing for non-even number of pages.The text was updated successfully, but these errors were encountered: