Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.3.1
-
Fix Version/s: 6.3.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Support Case References:Support Case 14419:- https://icesoft.my.salesforce.com/5000g000020hTwD?srPos=0&srKp=500
Description
A community member has submitted a PDF that doesn't load at all, it just shows up as a black dot in the RI.
Activity
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #52867 | Tue Jan 08 21:13:24 MST 2019 | patrick.corless | pdf files and allow document loader to fall back on a linear traversal. |
Files Changed | ||||
![]() |
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 6.3.2 [ 13175 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #52869 | Wed Jan 09 20:59:03 MST 2019 | patrick.corless | |
Files Changed | ||||
![]() |
Support Case References | Support Case 14419:- https://icesoft.my.salesforce.com/5000g000020hTwD?srPos=0&srKp=500 |
The PDF the an xref offset error that is just bad enough to allow the catalog to be found by our parser and the root page tree. However any deeper into the xref table and parser starts kicking back primitives instead of the requested object.
To address this I've added some validation checks that are pretty low cost where the root page tree children are referenced and parsed by the object parser. If any of the object come back as none pages we switch over to linear traversal.
This sort of problem will be solved by a new object parser I've been working on for quite some time now.