Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.3
-
Fix Version/s: 5.0.4
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Salesforce Case Reference:
Description
The file in question contains two content stream for a page. The first content stream is zero length and the second contains the page data. When the first zero length stream is encountered we through an IO exception that kicks the content parser out of it's loop and we never process the second stream. Which in this case results in a blank page.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Updated the Page initPageContents() method to prune any streams that have zero bytes. This in effect keeps the Lexer from choking.