-
Enhancement
-
Resolution: Fixed
-
P4
-
10, 11, 12, 13, 14
-
b08
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8245299 | 13.0.4 | Tobias Hartmann | P4 | Resolved | Fixed | b02 |
JDK-8235392 | 11.0.7-oracle | Tobias Hartmann | P4 | Resolved | Fixed | b01 |
JDK-8234969 | 11.0.7 | Tobias Hartmann | P4 | Resolved | Fixed | b01 |
NativeLookup::lookup_critical_entry() calls lookup_critical_style() multiple times and each time the shared library is resolved and loaded again. We should factor the library handling code out.
See also this comment by Vladimir Ivanov:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-December/029489.html
See also this comment by Vladimir Ivanov:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-December/029489.html
- backported by
-
JDK-8234969 NativeLookup::lookup_critical_entry() should only load shared library once
- Resolved
-
JDK-8235392 NativeLookup::lookup_critical_entry() should only load shared library once
- Resolved
-
JDK-8245299 NativeLookup::lookup_critical_entry() should only load shared library once
- Resolved
- relates to
-
JDK-8191360 Lookup of critical JNI method causes duplicate library loading with leaking handler
- Resolved