JDK-8255845 : Memory leak in imageFile.cpp
  • Type: Bug
  • Component: tools
  • Sub-Component: jlink
  • Affected Version: 11.0.8,16
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-11-03
  • Updated: 2024-12-20
  • Resolved: 2020-12-03
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 11 JDK 13 JDK 15 JDK 16
11.0.11-oracleFixed 13.0.8Fixed 15.0.4Fixed 16 b28Fixed
Description
The char array allocated at
[open/src/java.base/share/native/libjimage/imageFile.cpp:172] is not
released, if find_location() [at line 180] returns true.
Comments
Fix request (13u): fix here, too, for consistency. Clean; no regressions found.
29-04-2021
Fix request (15u): should be fixed here, too. The patch applies clean. Tested with tier1 and jlink tests, no regressions found.
28-04-2021
Fix Request (11u): Please approve backporting this to 11u. The same issue is present there. JDK head patch applies clean. Risk should be low. Tested with tier1 and jlink tests. No regressions.
14-12-2020
Changeset: 66a2e709 Author: Evan Whelan <ewhelan@openjdk.org> Committer: Jim Laskey <jlaskey@openjdk.org> Date: 2020-12-03 15:28:42 +0000 URL: https://git.openjdk.java.net/jdk/commit/66a2e709
03-12-2020
Might be a dup of JDK-8253948. As noted in the discussion about that issue, the jimage file is opened at startup and should never be closed. However the jrtfs provider (used by IDEs and other tools to access the resources in a target run-time image) may run into this issue.
04-11-2020