Pdfparser Stops no Error, Font.php memory exhausted
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.7k
- Forks
- 579
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Allowed memory size of 134217728 bytes exhausted (tried to allocate 524288 bytes)
Font.php [line] => 199
(I know i can increase memory limit.)
This happens when i loop through a large amount of pdfs, but always on a specific document, if i remove it, the processes will continue and parse a lot more until it finds another similar doc. I have notice that those pdfs were created with pdf Nitro.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure while parsing the Nitro-created PDF that triggers the memory exhaustion, then inspect Font.php at line 199 and the surrounding font-parsing flow. Compare it with documents that parse successfully and determine what allows processing to continue without exhausting memory; done means the affected PDFs no longer stop the loop unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100