Bug ID: JDK-7129722 Possible memory leak during JVM initialization

Type: Bug
Component: hotspot
Sub-Component: runtime
Affected Version: 7u4

Priority: P3
Status: Closed
Resolution: Won't Fix
OS: os_x
CPU: generic

Submitted: 2012-01-13
Updated: 2017-02-09
Resolved: 2017-02-09

This bug shadows a JIRA bug created for the Mac OS X port at...

http://java.net/jira/browse/MACOSX_PORT-168

Here is the description from that bug:

Running java leaks several strings:

> MallocStackLogging=1 /Volumes/Work/jdk7-macosxport/macosx-port/build/macosx-universal/j2sdk-bundle/1.7.0.jdk/Contents/Home/bin/java <some program>

In another window:
> leaks <java PID>

Report attached.

No longer a priority; if this becomes a customer problem, then can re-visit. Closing as Will Not Fix
09-02-2017
This should be improved as part of our memory cleanup for JDK9. This should be platform independent.
11-12-2012
PUBLIC COMMENTS As David mentioned above, it is part of much bigger problem, this is part of much bigger effort to cleanup VM memory when jvm library is unloaded.
01-08-2012
PUBLIC COMMENTS The VM is known to dynamically allocate a number of strings during VM initialization which are used for the lifetime of the VM. These strings are never explicitly freed. Technically this is leak when the VM is loaded by another process and then "unloaded" but in that case we have a far bigger issue because the Java heap is not freed either - see 6966194.
13-01-2012

Relates :	JDK-7044160 - Property argument processing leaks memory
Relates :	JDK-6859079 - JNI_CreateJavaVM() terminates the process on error condition instead of returning error code
Relates :	JDK-6966194 - java heap memory not released when vm exits