| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2205095 | 7 | Vladimir Kozlov | P4 | Closed | Fixed | b125 |
| JDK-2205847 | 6u25 | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
Running multi-day testing to look for bad data in internal metadata, with
the flags:
-XX:+UnlockDiagnosticVMOptions -XX:+FullGCALot -XX:+GCALotAtAllSafepoints -XX:+VerifyBeforeGC -XX:+VerifyAfterGC -XX:+VerifyOops -client
I ran into the assertion
Assert(_no_handle_mark_nesting==0,"allocating handle inside NoHandleMark"
the flags:
-XX:+UnlockDiagnosticVMOptions -XX:+FullGCALot -XX:+GCALotAtAllSafepoints -XX:+VerifyBeforeGC -XX:+VerifyAfterGC -XX:+VerifyOops -client
I ran into the assertion
Assert(_no_handle_mark_nesting==0,"allocating handle inside NoHandleMark"
- backported by
-
JDK-2205847 Assert(_no_handle_mark_nesting==0,"allocating handle inside NoHandleMark"
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-6852342 GC-a-lot feature should be NoHandleMark-aware
-
- Open
-