memory leak in JavaStar
I am currently using JavaStar 1.2 evaluation copy, I am testing Java Applications, I keep getting java.lang.outofmemory on my client side, I did edit my batch file and use whatever been suggested as: java javastar -J-noasyncgc -J-verbosecgc -J-ms4m -J-mx128m
This would set the minimum stack size to 4 megabytes, and the maximum stack size to 128 megabytes ( PP200, 128MBRAM).
If I watch the Memory in the WINNT TaskManager from script to script , it keeps increasing arithmetically, seems that javastar hoggs a tremendous amount of memory ,
Do anyone know how to release this memory ?
I did try this: in a test run, I have created a node at the very end which does a forced garbage collection System.gc(); See if this causes the memory usage to stay more constant, but this didn't resolve the problem.
I know that I shouldn't be calling the garbage collector because it is
called automatically. It seems that the garbage collector is not working.
I am using javastar 1.2 and jdk 1.1.7B.
I did try to run the whole test suite manually and no leak have been found, only a leak through javastar.
Am I missing any additional commands in the batch file?
Any ideas, thoughts or suggestions on how to solve this memory leak
problem is greatly appreciated
Re: memory leak in JavaStar
Try using -nojit
java -nojit -J-mx128m
Also check your swing and make sure you are running the latest swing