-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0, 5.0, 6u23, 6u38, 7, 9
-
b52
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084546 | emb-9 | Sergey Bylokhov | P4 | Resolved | Fixed | team |
JDK-8086872 | 8u65 | Sergey Bylokhov | P4 | Resolved | Fixed | b01 |
JDK-8078680 | 8u60 | Sergey Bylokhov | P4 | Resolved | Fixed | b14 |
JDK-8138086 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8079974 | emb-8u60 | Sergey Bylokhov | P4 | Resolved | Fixed | team |
The API doc for ImageWriter.abort() claims that every write operation must call clearAbortRequest at the begining. This is not supposed to be happening for JPG. When abort is invoked on a ImageWriter and the same writer is used to write the image again, the second write operation gets aborted immediately. This works fine for all other formats. Hence the abort flag must be reset at the begining of every write operation.
This is reproducible on all the platforms since JDK1.4.
I have attached a sample code. Execute the sample code and pass the image format as JPG. You would notice that the second write operation initiated after aborting the first one, also gets aborted immediately.
This is reproducible on all the platforms since JDK1.4.
I have attached a sample code. Execute the sample code and pass the image format as JPG. You would notice that the second write operation initiated after aborting the first one, also gets aborted immediately.
- backported by
-
JDK-8078680 abort flag is not cleared for every write operation for JPEG ImageWriter
-
- Resolved
-
-
JDK-8079974 abort flag is not cleared for every write operation for JPEG ImageWriter
-
- Resolved
-
-
JDK-8084546 abort flag is not cleared for every write operation for JPEG ImageWriter
-
- Resolved
-
-
JDK-8086872 abort flag is not cleared for every write operation for JPEG ImageWriter
-
- Resolved
-
-
JDK-8138086 abort flag is not cleared for every write operation for JPEG ImageWriter
-
- Resolved
-