JDK-8002273 : NMT to report JNI memory leaks when -Xcheck:jni is on
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs25
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2012-11-05
- Updated: 2014-06-26
- Resolved: 2012-11-10
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 7 | JDK 8 | Other |
|---|---|---|
7u40Fixed  |
8Fixed |
hs24Fixed |
Description
This bug is related to JDK-8001743. When 3rd party thread attaches JVM, but does not deattach JVM before it exits, that causes JVM to leak JavaThread object. NMT has the capability to capture the scenarios, it should report the problem when -Xcheck:jni is enabled.