JDK-8008555 : Debugging code in compiled method sometimes leaks memory
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Priority: P5
- Status: Resolved
- Resolution: Fixed
- Submitted: 2013-02-20
- Updated: 2023-07-21
- Resolved: 2013-03-18
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
+VerifyOops allocates string for messages on the C heap and they never get freed when the code for the methods is destroyed. Some support should exist for strings that have the same lifetime and the code that use them. CodeComments support addresses a similar problem and some of it could be extended.
Comments
|