JDK-8259869 : [macOS] Remove desktop module dependencies on JNF Reference APIs
- Type: Bug
- Component: client-libs
- Affected Version: 17
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-01-17
- Updated: 2025-01-16
- Resolved: 2021-01-22
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 11 | JDK 13 | JDK 15 | JDK 17 |
|---|---|---|---|
| 11.0.12-oracleFixed | 13.0.8Fixed | 15.0.4Fixed | 17 b07Fixed  |
Related Reports
|
Relates :
|
Description
JNF has a number of APIs that deal with JNI References : These : which add no value to the direct JNI call and can be directly replaced JNFNewGlobalRef JNFDeleteGlobalRef JNFNewWeakGlobalRef JNFDeleteWeakGlobalRef And these which just require a bit of extra handling because they create Cocoa class instances that will ensure the Java Refs are cleared when the carrier object is freed. JNFJObjectWrapper JNFWeakJObjectWrapper There seem to be simpler ways to free all the cases we have.
Comments
|