Details
-
Bug
-
Resolution: Fixed
-
P3
-
7, 8, 10, 11
-
b01
-
x86
-
os_x
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8234630 | 11.0.7-oracle | Kiran Sidhartha Ravikumar | P3 | Resolved | Fixed | b01 |
JDK-8228879 | 11.0.5 | Brian Burkhalter | P3 | Resolved | Fixed | b02 |
JDK-8228885 | openjdk8u232 | Brian Burkhalter | P3 | Resolved | Fixed | master |
Description
A DESCRIPTION OF THE PROBLEM :
When sun.nio.ch.UnixAsynchronousSocketChannelImpl is closed while a read() is pending, the field "readHandler" isn't set to null. This prevents a surrounding class from being garbage collected.
FREQUENCY : always
When sun.nio.ch.UnixAsynchronousSocketChannelImpl is closed while a read() is pending, the field "readHandler" isn't set to null. This prevents a surrounding class from being garbage collected.
FREQUENCY : always
Attachments
Issue Links
- backported by
-
JDK-8228879 (aio) Closed AsynchronousSocketChannel keeps completion handler alive
-
- Resolved
-
-
JDK-8228885 (aio) Closed AsynchronousSocketChannel keeps completion handler alive
-
- Resolved
-
-
JDK-8234630 (aio) Closed AsynchronousSocketChannel keeps completion handler alive
-
- Resolved
-
- links to