JDK-8296270 : Memory leak in ClassLoader::setup_bootstrap_search_path_impl
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9,11,17,19,20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-11-03
  • Updated: 2022-11-07
  • Resolved: 2022-11-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 20
20 masterFixed
Related Reports
Relates :  
JDK-8263421 - Module image file is opened twice during VM startup
Relates :  
JDK-8154239 - -Xbootclasspath/a breaks exploded build
Description
Colleague Justin King (jcking@google.com) made LeakSanitizer working with HotSpot, and identified a memory leak. ClassLoader::setup_bootstrap_search_path_impl() leaks a single ClassPathEntry, which should be deleted. This was present after JDK-8263421, but it is possibly introduced since JDK-8154239.
Comments
Changeset: 556377a0 Author: Man Cao <manc@openjdk.org> Date: 2022-11-07 03:53:32 +0000 URL: https://git.openjdk.org/jdk/commit/556377a0583b519ac191675c2b078f1a2efe2f72
07-11-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10973 Date: 2022-11-04 01:20:41 +0000
04-11-2022
Per suggestion from [~jiangli], I've splitted this up into two bugs as they are different leaks. The other is JDK-8296347.
04-11-2022
LeakSanitizer also identified MDO extra_data_lock leak fixed by JDK-8232112. However, it is likely benign as it is mainly due to shutdown code not destructing the object.
03-11-2022