| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8195693 | 11 | Tom Rodriguez | P2 | Resolved | Fixed | b01 |
| JDK-8197759 | 10u-cpu | Tom Rodriguez | P2 | Resolved | Fixed | master |
| JDK-8200928 | 10.0.2 | Unassigned | P2 | Resolved | Fixed | b01 |
| JDK-8195956 | 10.0.1 | Tom Rodriguez | P2 | Resolved | Fixed | b01 |
InspectedFrame.materializeVirtualObjects allows non-lazy materialization of a deoptimization by forcing the allocation of escape analyzed objects. This is accomplished by allocating those objects early and using jvmtiDeferredLocalVariableSet to write the into the deoptimized frame state. The current logic only writes to the locals and ignores any references to those VirtualObjects on the stack or the lock stack. The machinery must be expanded to cover those values.
- backported by
-
JDK-8195693 InspectedFrame.materializeVirtualObjects only updates locals with new objects
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-