JDK:1.2.2->Memory leaks in Class loader, Jar handling parts
From: qazmlp (qazmlp1209_at_rediffmail.com)
Date: 02/10/04
- Next message: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Previous message: Robert Klemme: "Re: Is returning ResultSet possible?"
- Next in thread: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Reply: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Reply: Andrew Thompson: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 10 Feb 2004 07:21:52 -0800
Has anybody noticed the memory leaks due to the class loader,Jar
handling parts of Java?
The heap profiling that I did for my Java process reports huge leaks
in these areas.
Here are some of the sample stacks that HAT reports:
1)
Stack
-----
TRACE 6924:
java/lang/String.<init>(String.java:Compiled method)
java/util/jar/Manifest.parseName(Manifest.java:Compiled method)
java/util/jar/Manifest.read(Manifest.java:Compiled method)
java/util/jar/Manifest.<init>(Manifest.java:Compiled method)
java/util/jar/JarFile.getManifest(JarFile.java:Compiled method)
sun/misc/URLClassPath$JarLoader.getClassPath(URLClassPath.java:Compiled
method)
sun/misc/URLClassPath.getLoader(URLClassPath.java:Compiled method)
sun/misc/URLClassPath.getResource(URLClassPath.java:Compiled method)
java/net/URLClassLoader$1.run(URLClassLoader.java:Compiled method)
java/net/URLClassLoader.findClass(URLClassLoader.java:Compiled
method)
Memory dump
-------------
percent live alloc'ed stack class
rank self accum bytes objs bytes objs trace name
132 0.10% 66.16% 54888 593 54888 593 6924 [C
2)
Stack
-----
TRACE 2776:
java/lang/String.<init>(String.java:Compiled method)
java/util/jar/Manifest.parseName(Manifest.java:Compiled method)
java/util/jar/Manifest.read(Manifest.java:Compiled method)
java/util/jar/Manifest.<init>(Manifest.java:Compiled method)
java/util/jar/JarFile.getManifest(JarFile.java:Compiled method)
sun/net/www/protocol/jar/URLJarFile.isSuperMan(URLJarFile.java:115)
sun/net/www/protocol/jar/URLJarFile.getManifest(URLJarFile.java:Compiled
method)
java/util/jar/JarFile.getInputStream(JarFile.java:Compiled method)
sun/net/www/protocol/jar/JarURLConnection.getInputStream(JarURLConnection.java:124)
java/net/URL.openStream(URL.java:818)
Memory dump
-------------
percent live alloc'ed stack class
rank self accum bytes objs bytes objs trace name
164 0.08% 69.06% 42312 452 42312 452 2776 [C
There are 30-40 such similar stacks shown in the report.
Here is the JDK version that I use:
java version "1.2.2"
Solaris VM (build Solaris_JDK_1.2.2_08, native threads, sunwjit)
Is this a known leak?
Please share if you have any information on this.
Thanks!
- Next message: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Previous message: Robert Klemme: "Re: Is returning ResultSet possible?"
- Next in thread: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Reply: Chris Smith: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Reply: Andrew Thompson: "Re: JDK:1.2.2->Memory leaks in Class loader, Jar handling parts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|