-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 19
-
b07
-
windows
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8281994 | 18.0.2 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
JDK-8281196 | 18.0.1 | Matthias Baesken | P4 | Resolved | Fixed | b06 |
JDK-8293073 | 17.0.6-oracle | Yoshiki Sato | P4 | Resolved | Fixed | b01 |
JDK-8281019 | 17.0.3 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
JDK-8280935 | 15.0.7 | Olga Mikhaltcova | P4 | Resolved | Fixed | b01 |
JDK-8280934 | 13.0.11 | Olga Mikhaltcova | P4 | Resolved | Fixed | b01 |
JDK-8293072 | 11.0.18-oracle | Yoshiki Sato | P4 | Resolved | Fixed | b01 |
JDK-8281804 | 11.0.15 | Matthias Baesken | P4 | Resolved | Fixed | b02 |
The leak only happens when DefaultProxySelector is used (java.net.useSystemProxies=true) and a proxy is used (the connection is not direct).
Reported by clang-tidy.
- backported by
-
JDK-8280934 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8280935 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8281019 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8281196 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8281804 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8281994 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8293072 Memory leak in DefaultProxySelector
- Resolved
-
JDK-8293073 Memory leak in DefaultProxySelector
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/fe17b44f
-
Commit openjdk/jdk13u-dev/43ebdb34
-
Commit openjdk/jdk15u-dev/e95ff4df
-
Commit openjdk/jdk17u-dev/869bb36c
-
Commit openjdk/jdk18u/1f039b3e
-
Commit openjdk/jdk/fe77250f
-
Review openjdk/jdk11u-dev/821
-
Review openjdk/jdk13u-dev/320
-
Review openjdk/jdk15u-dev/164
-
Review openjdk/jdk17u-dev/135
-
Review openjdk/jdk18u/12
-
Review openjdk/jdk/7172