Details
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8285098 | 8u42 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b02 |
Description
Reference objects cannot be meaningfully cloned. For example when cloning a WeakReference object that is pending for enqueuing, what state should the cloned reference object be? Should the referent of the newly cloned reference be considered as a strongly reference?
A new Reference object can be created via its constructor and a newly reference object has no relationship with any existing reference objects with the same referent.
This proposes not to support cloning of Reference object.
A new Reference object can be created via its constructor and a newly reference object has no relationship with any existing reference objects with the same referent.
This proposes not to support cloning of Reference object.
Attachments
Issue Links
- backported by
-
JDK-8285098 (ref) Reference object should not support cloning
-
- Resolved
-
- csr for
-
JDK-8202260 (ref) Reference objects should not support cloning
-
- Closed
-
- relates to
-
JDK-8285690 CloneableReference subtest should not throw CloneNotSupportedException
-
- Resolved
-
-
JDK-8202631 JVM_Clone to throw CloneNotSupportException for Reference object
-
- Resolved
-
(1 links to)