Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.3.2
-
Fix Version/s: 4.3.3
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:-
Description
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
It turns out that there is some junk added to the top of the file which is throwing the xref object indexes off. The content parser handles this correctly but parsing the complete file and adding all the document object to the library. The problem arises for xform objects in which they clean up after them selves and removed the associated resources from the library. Subsequent calls toget the objects force the library to reload the objects via the cross reference table which is already know to be corrupt and the image fails to load.
The image in question is part of an xobject that is shared and referenced for each page which expains why it goes missing after the first page. .
I have a potential fix for this which calculates the offset of the junk at the start of the file and appends the xref offsets calculations. I'll have to run this change though QA before I can mark it as fixed.
Marking as resolved.
The image in question is stored in an xobject and is shared between each of the pages. For some reason our Lazy object parser can't find the object after the initial load. This appears to be a bug with how we handle shared resources. This should be fairly easy to address.