Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.0
-
Fix Version/s: 5.1.1
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:org.icepdf.core.imageProxy=true
-
Support Case References:Support Case #12876 - https://icesoft.my.salesforce.com/5007000000dAoFa
-
Workaround Description:org.icepdf.core.imageProxy=false
Description
A client has reported deadlock state when doing image captures with the image proxy enabled. The capture is relatively straight forward only using a single thread for the pageCapture calls and the default image proxy of 4 threads.
Hopefully after getting a full thread dump we can get a better ideas as the the conditions for this to occur.
Hopefully after getting a full thread dump we can get a better ideas as the the conditions for this to occur.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
While upgrading the content set for QA I came a cross a few files that where causing the ImageProxy to get in a wait state. As a result I update the ImageReference to notifyAll when an image future task finished. I also did some work around the inline imageCache.
Show
Patrick Corless
added a comment - While upgrading the content set for QA I came a cross a few files that where causing the ImageProxy to get in a wait state. As a result I update the ImageReference to notifyAll when an image future task finished. I also did some work around the inline imageCache.
QA is running correctly with the new content set.