Hi,
The memory usage seems to come from
jit-temp-data: Nr 179 Mem 8980K, which doesn't get freed as it should be, so it's impossible to run with less then -mx 16M. I think the gc should try to free jit temp data when it runs out of memory. Tim, Helmer, what do you think?
The GC doesn't track this, its kept around in a pool which isn't freed if it passes some threshold.
So it would require either a change to the gc to track it (which I though it did, since the (re/de)allocations already happen through the gc interface) or a change in the jitter (jit3) to free temp data when it's not needed any more (after jitting a method? after a certain period of time?), right?
cheers, dalibor topic
_______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
