JDK-8204505 : Performance: jweak references not suitable for robust cache architecture
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Other
- Submitted: 2018-06-06
- Updated: 2019-05-01
- Resolved: 2018-11-06
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 12 |
|---|
12Resolved  |
Related Reports
|
Blocks :
|
|
|
Cloners :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Performance: jweak references not suitable for robust cache architecture #1 Contrary to the expectations, jweak objects that are destroyed with DeleteWeakGlobalRef() take more GC time than alive one, but with dead objects (see attached test case) #2 DeleteWeakGlobalRef() does not actually free the memory #3 jweaks are processed single threaded by the GC
Comments
|