Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 6.3.1
-
Component/s: Core/Parsing, Font Engine
-
Labels:None
-
Environment:Pro
Description
For some time now we've seen from time to time a stack exception when when doing a CMap initialization. Duplicating this is pretty difficult as it would appear to be a concurrency issue. A closer look a the CMap.getInnstance() call seems to indicate that there could be some concurrency issues.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The root of the problem is in the ImageStream getImage() call is putting the decoded image in the image pool. When the blurredImageReference or other types runs if first checks to see if the image is already in the pool before applying the scale. The overlap doesn't happen every time, likely the future call is slow to start or some other timing issue.
I've make sure that the imagepool is only mutable from the CachedImageReference which makes more sense in the bigger picture.
Show
Patrick Corless
added a comment - The root of the problem is in the ImageStream getImage() call is putting the decoded image in the image pool. When the blurredImageReference or other types runs if first checks to see if the image is already in the pool before applying the scale. The overlap doesn't happen every time, likely the future call is slow to start or some other timing issue.
I've make sure that the imagepool is only mutable from the CachedImageReference which makes more sense in the bigger picture.
Making as fixed.