You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately I cannot share the problematic file, but JHOVE throws an error
PDF-HUL-110 "Invalid object number or object stream"
on a stream object whose dictionary looks standard conformant. All stream-objects within the PDF can be uncompressed via qpdf --stream-data=uncompress, I therefore do not suspect an error within the object stream itself.
Looking at the object that the offset is reported for, it contains an /Extend entry:
That's not a problem and obj 34 is a stream object itself that looks valid.
I have the suspicion that the /Extend entry causes a false positive for this error.
The text was updated successfully, but these errors were encountered:
I'm still encountering this, however, with other PDF-hul error messages. Most recently a PDF-hul 2 "Invalid destination object", but the dictionary looked the same: << /Extends 18843 0 R /Filter /FlateDecode /First 354 /Length 1534 /N 33 /Type /ObjStm >>
@carlwilson - is it true that this can appear for different PDF-hul errors? I guess the original PDF-hul 110 might have gotten shifted to PDF-hul 2 somewhere between April 2021 and today.
Unfortunately I cannot share the problematic file, but JHOVE throws an error
PDF-HUL-110 "Invalid object number or object stream"
on a stream object whose dictionary looks standard conformant. All stream-objects within the PDF can be uncompressed via qpdf --stream-data=uncompress, I therefore do not suspect an error within the object stream itself.
Looking at the object that the offset is reported for, it contains an /Extend entry:
That's not a problem and obj 34 is a stream object itself that looks valid.
I have the suspicion that the /Extend entry causes a false positive for this error.
The text was updated successfully, but these errors were encountered: