Details
-
Bug
-
Status: Resolved
-
P4
-
Resolution: Fixed
-
8-shenandoah, 11.0.9, 15, 16
-
b33
-
generic
-
generic
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8249730 | 16 | Roman Kennke | P4 | Resolved | Fixed | b07 |
JDK-8250199 | 15.0.2 | Roman Kennke | P4 | Resolved | Fixed | b01 |
JDK-8250498 | 15.0.1 | Roman Kennke | P4 | Resolved | Fixed | b03 |
JDK-8261314 | 11.0.11 | Roman Kennke | P4 | Resolved | Fixed | b02 |
Description
DirectBufferAllocTest is unreliable when running with +ExplicitGCInvokesConcurrent, because allocating DBB spreads System.gc() calls all over concurrent GC cycles. It becomes more reliable when running with -ExplicitGCInvokesConcurrent. (Some GCs e.g. Shenandoah default to +ExplicitGCInvokesConcurrent)
Attachments
Issue Links
- backported by
-
JDK-8249730 (bf) Force DirectBufferAllocTest to run with -ExplicitGCInvokesConcurrent
-
- Resolved
-
-
JDK-8250199 (bf) Force DirectBufferAllocTest to run with -ExplicitGCInvokesConcurrent
-
- Resolved
-
-
JDK-8250498 (bf) Force DirectBufferAllocTest to run with -ExplicitGCInvokesConcurrent
-
- Resolved
-
-
JDK-8261314 (bf) Force DirectBufferAllocTest to run with -ExplicitGCInvokesConcurrent
-
- Resolved
-