I did that, but that doesn't help. I set the size to 64 megs. but the
VM size behaved the same way. Please let me know if there's something
else that can be done.
Also, can you please point me to the diff between the VM size and the
heap size?
On May 30, 4:53 pm, Joshua Cranmer <Pidgeo...@[EMAIL PROTECTED]
> wrote:
> parminde...@[EMAIL PROTECTED]
wrote:
> > I used JProf to see that my Swing app has 40 megs of heap allocated to
> > it. However, over time VM size of the java.exe process keeps on rising
> > and at times hits 300 megs. I understand that the JVM may be using
> > this memory for internal purposes. But is there a way to limit the
> > size to which the VM grows?
>
> > In short if I need to tell my customers that when they run my app the
> > VM size will not grow higher than some limit. Are there any VM
> > parameters I can use to ensure this.
>
> From Sun's java command line reference (keep in mind: this is a
> 'non-standard' option, and is only guaranteed for Java versions ~ 1.1 -
6):
>
> -Xmxn
> Specify the maximum size, in bytes, of the memory allocation pool.
> This value must a multiple of 1024 greater than 2MB. Append the letter k
> or K to indicate kilobytes, or m or M to indicate megabytes.
> (e.g. -Xmx40m)
>
> This is the URL for the Java 6 version of the command
line:http://java.sun.com/javase/6/docs/technotes/tools/windows/java.html#n...
>
> and the earlier versions can be obtained by changing the javase/6/ to
> j2se/1.{5,4.2,?}/
|
