Hi!
Does anyone have a solution or workaround for the following problem;
We run a GUI-application for 48 hours. We have intensive CORBA communication
and presents the result in a map (based on ILOG software). We have tested
our application with JProbe and it seems like we haven't got any memory
leaks.
We start our application with an initial heap of 256M and a maximum heap of
256 M. When we check in the Windows task manager we see that the jvm process
consumes roughly 340 M. The total memory consumed in the windows system sums
up approximately to the total som of memory used by the kernel and the
processees.
After 48 hours we check the task manager again. Now the memory consumed in
the system is 1.2 GB. According to the task manager the java process has
still 240 M allocated. The total sum of all process and kernel memory
doesn't match 1.3 GB by far.
But when I kill the JVM all memory is made free! It seems like the JVM
itself holds memory that is not reported free to the operating system.
br
/Anders Jansson
Mark A. Washburn - 26 Feb 2004 17:08 GMT
If you get then same results with Linux then
"JVM doesn't free memory on ..." is a reasonable
question, otherwise, however, the question maybe
a problems with Win 2000, restating the assertion
as "Windows 2000 doesn't free memory deallocated
by JVM X.X"
Also, have you tried forcing GC?
Have you tried Thread.sleep(XXXX)? ( to permit
Windows 2000 time to garbage collect it's heap.)
Mark A. Washburn
maw
http://mywebpage.netscape.com/mawcowboy/homepage.html
http://www.geocities.com/dolphinconsultant/myforth.html