JDK-6896905 : jnistress005 fails with a bad oop with compressed oops and CMS
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs17
- Priority: P3
- Status: Closed
- Resolution: Cannot Reproduce
- OS: generic
- CPU: generic
- Submitted: 2009-10-30
- Updated: 2013-03-05
- Resolved: 2013-03-05
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 8 |
|---|
8Resolved  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
I've seen jnistress005 fail once during nighly testing with a synchronization (by the looks of it) issue, as well as maybe a JNI handle issue too. With compressed oops going in with no-perm-gen this would be a good time to see if this bug is still pertinent. Christian offered to help find test history if that would be helpful.
Comments
|