-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 8-shenandoah, 11.0.9, 14
-
Component/s: hotspot
-
b32
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8237025 | 15 | Erik Österlund | P2 | Resolved | Fixed | b06 |
| JDK-8237411 | 14.0.1 | Unassigned | P2 | Resolved | Fixed | b01 |
When the stack is walked and e.g. locals are turned into StackValues, it might be that said local was made a constant oop by the JIT. In such cases, it is read from the nmethod using ON_STRONG_OOP_REF | AS_NO_KEEPALIVE. However, these oops need to be kept alive when concurrent marking is ongoing.
While I haven't seen crashes obviously linked to this yet, I don't think we should wait until we do, because it certainly will eventually.
While I haven't seen crashes obviously linked to this yet, I don't think we should wait until we do, because it certainly will eventually.
- backported by
-
JDK-8237025 G1: Stack walking API can expose AS_NO_KEEPALIVE oops
-
- Resolved
-
-
JDK-8237411 G1: Stack walking API can expose AS_NO_KEEPALIVE oops
-
- Resolved
-