JDK-8259374 : Make ThreadInVMfromNative have ResetNoHandleMark
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-01-07
- Updated: 2021-01-19
- Resolved: 2021-01-12
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 17 |
|---|
17 b05Fixed  |
Related Reports
|
Relates :
|
Description
If ThreadInVMfromNative has a ResetNoHandleMark, then all these places that make the transition do not have to add this. JVM code that is in native state has a NoHandleMark because having Handles and oops are unsafe, but when the code transitions to the VM, we can now have Handles. This cleans up a lot of these call sites. (Splitting this out of the linked bug).
Comments
|