JDK-8233027 : OopMapSet::all_do does oms.next() twice during iteration
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 11.0.9-oracle,14
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2019-10-25
- Updated: 2021-02-03
- Resolved: 2019-10-25
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 11 | JDK 13 | JDK 14 |
|---|---|---|
11.0.9-oracleFixed  |
13.0.6Fixed | 14 b21Fixed |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
Description
It seems to be introduced by JDK-8232083. New code does oms.next() twice:
for (OopMapStream oms(map); !oms.is_done(); oms.next()) { // <--- here
OopMapValue omv = oms.current();
if (omv.type() != OopMapValue::derived_oop_value) {
continue;
}
...
if (base_loc != NULL && *base_loc != NULL && !CompressedOops::is_base(*base_loc)) {
derived_oop_fn(base_loc, derived_loc);
}
oms.next(); // <--- then here
}
We are seeing some weird, random, intermittent test failures with Shenandoah in jdk/jdk recently, this might explain it.
Comments
|