[Poppler-bugs] [Bug 44085] pdfinfo/pdffonts cannot process >2GB files

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=44085

--- Comment #24 from Adrian Johnson <ajohnson at redneon.com> ---
Created attachment 72449
  --> https://bugs.freedesktop.org/attachment.cgi?id=72449&action=edit
fix uninitialised memory

I've found the rendering differences for bug-poppler26533.pdf to be caused by
uninitialised memory in splash. This patch fixes the problem.

I don't have any idea why tauya.f8.pdf is showing differences however I suspect
it is an existing problem that is just failing in a different way with the
large file patches. The tauya.f8 pdf is very broken. It has a broken font
(corrupted Flate stream). Poppler does not seem to have error detection in the
Flate decompression and renders mostly garbage. Ghostscript detects the broken
stream and substitutes a different font resulting in what appears to be correct
output. If I remove the font descriptor from the pdf forcing poppler to
substitute the font, the output is the same as ghostscript with no regression
when using the large font patches. Acroread complains the font is broken and
displays garbage.

So at this point I think the patches are ready for review.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/poppler-bugs/attachments/20130103/e7500ed5/attachment.html>