Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.3
-
Fix Version/s: 6.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Support Case References:Support Case #13979 - https://icesoft.my.salesforce.com/5007000001gNspT
Description
A client has sent in new example of the dash array issue that is causing Java2d a segment fault. We have seen this in the past the case examples have only contains two item dash arrays. The PDF in question has the following definitions:
0.0 [3.8085938, 76203.805]
0.0 []
0.0 [133354.4, 177804.4, 4.445312, 177804.4]
0.0 [5.714844, 114305.7]
0.0 [133354.4, 177804.4, 4.445312, 177804.4]
0.0 [5.714844, 114305.7]
The probably is related to the 4.4 and 4.7 values. These values appear not to have been scaled to PDF space are causing the segment fault. If the values are multiplied by 1000 we get the correct values. The trick however is how to detect the error when encountered.
0.0 [3.8085938, 76203.805]
0.0 []
0.0 [133354.4, 177804.4, 4.445312, 177804.4]
0.0 [5.714844, 114305.7]
0.0 [133354.4, 177804.4, 4.445312, 177804.4]
0.0 [5.714844, 114305.7]
The probably is related to the 4.4 and 4.7 values. These values appear not to have been scaled to PDF space are causing the segment fault. If the values are multiplied by 1000 we get the correct values. The trick however is how to detect the error when encountered.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as fixed.
Show
Patrick Corless
added a comment - Marking as fixed.
The new adjustment technique is to do a read a head on the dash array and try and detect a large value change. This could still be error prone but it passes all our corner cases for now. If the read a head detected a need for adjustment then we scale any value less then 10. Seems arbitrary but it's the only pattern we can act on for now.