Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 83176 invoked from network); 21 Nov 2002 16:34:35 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Nov 2002 16:34:35 -0000 Received: (qmail 14268 invoked by uid 97); 21 Nov 2002 16:35:30 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 14252 invoked by uid 97); 21 Nov 2002 16:35:29 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 14239 invoked by uid 98); 21 Nov 2002 16:35:27 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DDD0B59.2F962C50@labs.gte.com> Date: Thu, 21 Nov 2002 11:35:37 -0500 From: peter lin X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Javac memory leak References: <000d01c29179$3742cbf0$970510ac@jtrollingerxp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is from the examples jsp right? or are they from your webapp? the latest optimizeit has a leak finder feature. you may want to download the trail version and give it a shot. from the data it looks like a lot of objects are promoted to old memory from heap. It doesn't necessarily constitute a memory leak though. if you use a lot of static variables, that could easily account for objects getting promoted to old memory peter John Trollinger wrote: > > When I run the examples with -verbose:gc this is what I get (just the > snippits at the end) > > >From uncompiled jsp pages > > [GC 14707K->13665K(28412K), 0.0059002 secs] > [GC 15521K->15518K(28412K), 0.0128997 secs] > [GC 17374K->16086K(28412K), 0.0092266 secs] > [GC 17942K->16258K(28412K), 0.0086307 secs] > [GC 18114K->16213K(28412K), 0.0046327 secs] > [GC 18069K->17934K(28412K), 0.0114056 secs] > [GC 19790K->19672K(28412K), 0.0155838 secs] > > Did you see me on the stderr window? > > Did you see me on the browser window as well? > > [GC 21520K->20092K(28412K), 0.0094920 secs] > [GC 21947K->20095K(28412K), 0.0075890 secs] > [GC 21951K->21758K(28412K), 0.0131385 secs] > [GC 23614K->23528K(28412K), 0.0137372 secs] > [GC 25384K->23769K(28412K), 0.0079125 secs] > [GC 25625K->24336K(28412K), 0.0073652 secs] > [GC 26192K->26170K(28412K), 0.0153369 secs] > [GC 28026K->27460K(29436K), 0.0190963 secs] > [Full GC 27460K->15538K(29436K), 0.2839948 secs] > [GC 17394K->15720K(28412K), 0.0060262 secs] > [GC 17575K->15746K(28412K), 0.0046218 secs] > [GC 17602K->15745K(28412K), 0.0027241 secs] > [GC 17601K->15745K(28412K), 0.0025604 secs] > [GC 17601K->15746K(28412K), 0.0026679 secs] > Stopping service Tomcat-Standalone > > >From compiled jsp pages > > [GC 11356K->10577K(14028K), 0.0061505 secs] > [GC 11532K->11034K(14028K), 0.0046978 secs] > [GC 11994K->11305K(14028K), 0.0060575 secs] > [GC 12265K->11341K(14028K), 0.0059876 secs] > [GC 12297K->11396K(14028K), 0.0065578 secs] > [GC 12356K->11538K(14028K), 0.0063572 secs] > [GC 12498K->11598K(14028K), 0.0040036 secs] > [GC 12558K->11965K(14028K), 0.0052529 secs] > > Did you see me on the stderr window? > > Did you see me on the browser window as well? > > [GC 12925K->12020K(14028K), 0.0046872 secs] > Stopping service Tomcat-Standalone > > As you can see there is about a 4 meg diff between the two > > This is using j2sdk 1.4.1 on windows XP with 512 ram using tomcat > 4.1.14LE > -- To unsubscribe, e-mail: For additional commands, e-mail: