Running the SwingMark benchmark harness repeatedly in the same VM shows there is a small memory leak. With 1.2 fcs, there was a very LARGE memory leak (several hundred k per run). With 1.2.2 build e this leak has been reduced to about 1k per run. This however is still unacceptable. Here is the data output from the -m option in SwingMark:

Used Memory HeapSize
1986704 3260408
2602696 5439480
2612832 5472248
2614064 5476344
2614560 5476344
2615912 5476344
2616664 5476344
2619232 5480440
2619856 5480440
2619624 5480440

As you can see, the used memory in the JavaHeap increased from 2614k to 2619k between runs 4 and 10.

I haven't get tracked down what is leaking, but I'm working on it.

Also, the SQE team's SwingBasher application (which is similar to SwingMark) is seeing probably related problems. It can currently only run for about 24 hours without failing due to out of memory problems. This is an improvement over 1.2 fcs, but it shoud run forever.

steve.wilson@eng Feb 3, 1999