-
Bug
-
Resolution: Fixed
-
P4
-
hs18
-
b01
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2193332 | 7 | Christian Thalinger | P4 | Closed | Fixed | b94 |
JDK-2197888 | 6u23 | Christian Thalinger | P4 | Closed | Fixed | b01 |
JDK-2199789 | 6u22m | Christian Thalinger | P4 | Closed | Fixed | b01 |
JDK-2197594 | 6u21p | Christian Thalinger | P4 | Closed | Fixed | b03 |
Gary Benson wrote:
Hi all,
The way Zero currently handles deoptimization can lead to methods
being freed while they are still being executed, with the obvious
consequences. This webrev fixes:
http://cr.openjdk.java.net/~gbenson/zero-deopt-fix/
I don't have a bug id for this.
Cheers,
Gary
Hi all,
The way Zero currently handles deoptimization can lead to methods
being freed while they are still being executed, with the obvious
consequences. This webrev fixes:
http://cr.openjdk.java.net/~gbenson/zero-deopt-fix/
I don't have a bug id for this.
Cheers,
Gary
- backported by
-
JDK-2193332 Zero deoptimizer changes
- Closed
-
JDK-2197594 Zero deoptimizer changes
- Closed
-
JDK-2197888 Zero deoptimizer changes
- Closed
-
JDK-2199789 Zero deoptimizer changes
- Closed
- relates to
-
JDK-6962193 Rebrand some Zero files
- Resolved