-
Enhancement
-
Resolution: Fixed
-
P3
-
11, 12, 13, 14
-
b11
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8230049 | 13.0.2 | Ivan Gerasimov | P3 | Resolved | Fixed | b01 |
| JDK-8230247 | 13.0.1 | Ivan Gerasimov | P3 | Resolved | Fixed | b07 |
| JDK-8230108 | 11.0.6-oracle | Ivan Gerasimov | P3 | Resolved | Fixed | b01 |
| JDK-8231519 | 11.0.6 | Claes Redestad | P3 | Resolved | Fixed | b01 |
| JDK-8230243 | 11.0.5-oracle | Ivan Gerasimov | P3 | Resolved | Fixed | b07 |
| JDK-8231300 | 11.0.5 | Claes Redestad | P3 | Resolved | Fixed | b09 |
When establishing protection domains during class load, we resolve the permissions needed to access a code source eagerly. This forces early initialization of FilePermission etc, which in turn initializes default file system and others. Since the permissions are not checked against unless a security manager has been installed, this is often done unnecessarily.
By doing the initialization lazily using a delegating implementation, we reduce number of classes loaded on many small apps by ~40.
By doing the initialization lazily using a delegating implementation, we reduce number of classes loaded on many small apps by ~40.
- backported by
-
JDK-8230049 Resolve permissions for code source URLs lazily
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8213406 (fs) More than one instance of built-in FileSystem observed in heap
-
- Resolved
-
(1 backported by, 1 relates to)