-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 13
-
b22
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8227243 | 11.0.6-oracle | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
| JDK-8230556 | 11.0.6 | Claes Redestad | P4 | Resolved | Fixed | b01 |
| JDK-8228348 | 11.0.5-oracle | Ivan Gerasimov | P4 | Resolved | Fixed | b02 |
| JDK-8230432 | 11.0.5 | Claes Redestad | P4 | Resolved | Fixed | b06 |
Some java.security properties will always be accessed even when there's no SecurityManager installed, which means we might load sun.security.util.SecurityProperties early in the bootstrap sequence. To improve startup - and keep it from regressing in a few key applications - we should avoid calling through AccessController when there's no SecurityManager installed.
Desugaring the lambda use here was also considered, but if we run with a SecurityManager installed we'll instantiate a few other lambdas during bootstrap so gain was not measurable.
Desugaring the lambda use here was also considered, but if we run with a SecurityManager installed we'll instantiate a few other lambdas during bootstrap so gain was not measurable.
- backported by
-
JDK-8227243 Improve startup behavior of SecurityProperties
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-