| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8310288 | 22 | Erik Österlund | P2 | Resolved | Fixed | b03 |
| JDK-8310436 | 21.0.1 | Erik Österlund | P2 | Resolved | Fixed | b02 |
ZGC (both generational and non-generational) use asynchronous unmapping. Today the amount of unmapping requests we can queue up is unbounded. This can lead to a classic consumer producer problem, where the consumer is slower than the producer, and we eventually run out of address space and have to shut down.
This issue seeks to focus on the unbounded nature of the asynchronous unmapping.
This issue seeks to focus on the unbounded nature of the asynchronous unmapping.
- backported by
-
JDK-8310288 ZGC: Unbounded asynchronous unmapping can lead to running out of address space
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8308783 ZGC: Asynchronous unmapping can lead to running out of address space
-
- Open
-
- links to
-
Commit
openjdk/jdk21/14c5091a
-
Commit
openjdk/jdk/4229baf9
-
Review
openjdk/jdk21/28
-
Review
openjdk/jdk/14513
(2 links to)