RE: [WDSCI-L] Java memory leak?

["Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>]

Couple things, first of all, as a performance thing, I have always hard-set
my virtual memory. The reason? Fragmentation it cuts away performance. As a
general rule of thumb, set it to twice as much as you have memory. But that
can be unrealistic, so in my case I have 512 MB or RAM and 768 MB of VM. 

Secondly, I have found that if I run MaxMem
(http://www.analogx.com/contents/download/system/maxmem.htm) you can more
easily clean up after WDSc more often. MaxMem is a little (about 1.5 mb
utility) that runs on your PC and cleans up lost memory. It does a good job
of it. Whenever I run WDSc, I run MaxMem. 

-----Original Message-----
From: Vern Hamberg 

Just got the version 5 upgrade. I am on Win XP SP1, 256 meg memory. Java 
version is

C:\Documents and Settings\Vern>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cn130-20020124 (JIT enabled: 
jitc)

Task Manager memory usage shows javaw's allocation growing constantly. This 
is while WDSC is running. When I got back to my machine, it was at 64meg 
(WDSC minimized), when I restored WDSC it jumped to 120meg and kept going. 
When I minimized WDSC again, down to 2meg, then grew very quickly (minutes) 
to 120meg, then a little while later down to 70meg or so, then grew again.

Is this normal? Is this garbage collection? I also had a message that 
virtual memory was running out - XP was adjusting it. Right now it says the 
commit charge is 952 meg with 399 meg committed.