Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 4.3.1
-
Fix Version/s: 5.0.0 alpha1, 5.0
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
Description
When the third page of the document in question is parsed a very strange initialization sequence begins. When handing the stroking tokens 'S' an 's' the method commonStroke is called, not to out of the ordinary here. But in the case of page three there is a tiling pattern being parsed.
tilingPattern.setParentGraphicState(graphicState);
tilingPattern.init();
In the above case the parent graphic state contains the tilingPattern as the fill. So when tilingPattern.init() is called an infinit loop starts, each call tries to initialize the same tiling pattern.
The quick and dirty way to avoid the look is to remove the setParentGraphicsState() . However further research into the PDF spec needs to be done to insure we're handing the graphics state correctly or if the PDF is malformed.
tilingPattern.setParentGraphicState(graphicState);
tilingPattern.init();
In the above case the parent graphic state contains the tilingPattern as the fill. So when tilingPattern.init() is called an infinit loop starts, each call tries to initialize the same tiling pattern.
The quick and dirty way to avoid the look is to remove the setParentGraphicsState() . However further research into the PDF spec needs to be done to insure we're handing the graphics state correctly or if the PDF is malformed.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion