JDK-6861660 : OopMapBlock count/size confusion
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs11
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-07-17
- Updated: 2010-04-28
- Resolved: 2010-04-28
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 6 | JDK 7 | Other |
|---|---|---|
6u18Fixed  |
7Fixed |
hs16Fixed |
Related Reports
|
Relates :
|
Description
Code in instanceKlass, classFileParser and elsewhere assumes that sizeof(OopMapBlock) <= sizeof(HeapWord), and thus confuses the count of oop map blocks with their size in words in several places. If OopMapBlock is made larger than a HeapWord, the VM crashes quickly.
Comments
|