-
Bug
-
Resolution: Fixed
-
P4
-
11.0.7-oracle, 15
-
b07
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8239329 | 14.0.2 | Claes Redestad | P4 | Resolved | Fixed | b01 |
| JDK-8239369 | 14.0.1 | Claes Redestad | P4 | Resolved | Fixed | b05 |
| JDK-8246547 | 13.0.4 | Claes Redestad | P4 | Resolved | Fixed | b04 |
| JDK-8237978 | 11.0.8-oracle | Claes Redestad | P4 | Resolved | Fixed | b01 |
| JDK-8239258 | 11.0.7-oracle | Claes Redestad | P4 | Resolved | Fixed | b05 |
| JDK-8238748 | 11.0.7 | Claes Redestad | P4 | Resolved | Fixed | b03 |
Cause appears to be the addition of a lambda to JarFile.<clinit>. Since the value is only read rarely and only in one place, it could be simplified to use the default ThreadLocal initial value (null):
- static final ThreadLocal<Boolean> isInitializing =
- ThreadLocal.withInitial(() -> Boolean.FALSE);
+ static final ThreadLocal<Boolean> isInitializing = new ThreadLocal<>();
.. with adjustments in the places that read. This recuperates the startup regression.
- backported by
-
JDK-8237978 Simplify JarFile.isInitializing
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Resolved
-
(1 backported by, 1 duplicates, 1 relates to)