| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045385 | 8u25 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b01 |
| JDK-8039389 | 8u20 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b10 |
| JDK-8053304 | emb-8u26 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b17 |
List verification code has been accidentally enabled in product builds in one place. This may impact performance and it should be changed to only perform verification in debug builds.
ConcurrentMark::completeCleanup() is currently calling _cleanup_list.verify_list(). This will unconditionally run the verification, even in product builds. This should be replaced with verify_optional() that only runs the verification code in debug builds.
ConcurrentMark::completeCleanup() is currently calling _cleanup_list.verify_list(). This will unconditionally run the verification, even in product builds. This should be replaced with verify_optional() that only runs the verification code in debug builds.
- backported by
-
JDK-8039389 List verification enabled in product builds
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-