Re: Memory "leak"?
nospam@invalid.invalid wrote:
As a test, try putting a System.gc() call inside the loop. Does the
memory use still tend to climb?
Thanks Patricia - I like simple litle gems like that.
The memory used stepped up quite quickly after I guess the first
System.gc(); line was called, but after that it climbed by 4KB only once and
now a full 10 minutes later, the memory usage is still the same. So in
conclusion, the memory went up by around 500KB by using the garbage
collector and then a further 4KB after the next loop, but then stabilised
(or at least as far as I can see).
Let's hope it stays that way. I'll check back on it in a few hours and if it
climbs again, I'll post back, but it seems that this might be fixed. Thanks
once again for that brilliant suggestion!
Note that you may not need the System.gc() call. If it is effective, it
means that the climbing memory is due to finalizable, but unfinalized,
objects. The JVM would have done GC anyway before running out of memory.
The explicit call is a quick way of finding out whether that GC call
would have found memory it could free, and the result suggests that it
could.
That said, it is possible that your trade-offs call for more time spent
doing GC and less memory use than the JVM's trade-offs. If so, it may be
worth doing GC once every N iterations, for some value of N.
Patricia