-
Bug
-
Resolution: Fixed
-
P4
-
11, 12
-
b18
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8226484 | 11.0.5-oracle | Martin Doerr | P4 | Resolved | Fixed | b02 |
| JDK-8213523 | 11.0.3 | Martin Doerr | P4 | Resolved | Fixed | master |
Since JDK-8198756, compiler threads are created/removed at runtime depending on the compile queue length.
They were supposed to be limited by the available memory, too, but there's a bug in the limiting function (missing braces).
We should also make this dependent on the available space in the code cache because it does not make sense to add more compiler threads if there is almost no space for compiled code and scratch buffers left (JDK-8177899).
They were supposed to be limited by the available memory, too, but there's a bug in the limiting function (missing braces).
We should also make this dependent on the available space in the code cache because it does not make sense to add more compiler threads if there is almost no space for compiled code and scratch buffers left (
- backported by
-
JDK-8213523 Compiler thread creation should be bounded by available space in memory and Code Cache
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
JDK-8198756 Lazy allocation of compiler threads
-
- Resolved
-