Summary: | crash with evince on opening pdf with : Not a JPEG file: starts with 0x02 0x00 | ||
---|---|---|---|
Product: | poppler | Reporter: | Thilo Pfennig <thilopfennig> |
Component: | general | Assignee: | Kristian Høgsberg <krh> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | aacid, newren |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
the file on which evince crashed
the similar PDF that does not crash |
Description
Thilo Pfennig
2005-05-16 02:04:59 UTC
Created attachment 2684 [details]
the file on which evince crashed
picture is license CC-by-sa1.0
Created attachment 2685 [details]
the similar PDF that does not crash
So the problem is that libjpeg does not like the jpeg inside the pdf. How was the crashing pdf produced? -Jeff The problem is that libjpeg is strict with jpeg format and adobe is not that much. The file that crashes begins the DCTStream with stream^M ^B^@3^@^@^@^C^@^EØ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^A^@^[^@^@^@ ^@^@^@^@^@^@^@^@^@^A^@^@^@^A^@^@^@^A^@^@^@^A^@^@^@^AÿØÿà^@^PJFIF when the good start is stream^M ÿØÿà^@^PJFIF You see there's a lot of "gargabe" before the ÿØ marker that is the start marker of a JPEG "file". I've made a way too hackish patch that fixes that, i suppose we can find a better way to plug our own marker function in libjpeg code so that this file is correctly read. We also can close this bug as INVALID as the pdf itself is faulty. Created attachment 3140 [details] [review] Proposed patch Created attachment 3141 [details] [review] Second attempt (In reply to comment #4) > We also can close this bug as INVALID as the pdf itself is faulty. > Well INVALID? ok, the PDF is faulty, but I think the optimum would be not to crash. Either give a note like "this PDF is faulty and cannot be displayed" or open it, nevertheless. I would think a crash should never happen? The bug is already fixed in cvs. |
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.