| Summary: | pdftoppm crashes on pdf | ||
|---|---|---|---|
| Product: | poppler | Reporter: | Ralph <ralph> |
| Component: | utils | Assignee: | poppler-bugs <poppler-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | File that causes the bug | ||
Split the PDF file with pdftoppm ??? I was describing the way that we reproduce it in our stack. If you use pdftoppm to split the file: pdftoppm -png "2012 TWELFTH NIGHT 11X17 OUTLINE.pdf" -f 1 -l 2 It seems to fail the same way. That does not split the pdf file, that renders it. pdfseparate splits the pdf ;-) pdftoppm -png "2012 TWELFTH NIGHT 11X17 OUTLINE.pdf" -f 1 -l 2 doesn't fail, it writes the png to the stdout as you asked it to do My apologies! Too much multitasking not enough focus on filing a good bug report. Let me carefully figure out exactly what the reproduction steps are. Sorry, the actual error I'm getting is: "Bogus memory allocation size" which is related to a previous bug I've filed with you. I'll close this bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 62939 [details] File that causes the bug Steps to reproduce: 1) Split the PDF file with pdftoppm 2) Attempt to run pdftoppm -png with the second page of the output to pdftoppm 3) pdftoppm crashes and spits a bunch of garbage (the png data?) to stdout Thanks!