JDK-7125516 : G1: ~ConcurrentMark() frees incorrectly
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs23
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-12-28
- Updated: 2013-09-18
- Resolved: 2012-03-29
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 |
|---|---|---|
7u4Fixed  |
8Fixed |
hs23Fixed |
Description
The ConcurrentMark desctructor _max_task_num which is a size_t and not a pointer to allocated memory. However, the ConcurrentMark desctructor is never called, so the biggest problem right now is that newer g++ compilers complain about this.
Comments
|