Batik uses soft reference caches, etc. So in general you can't tell much from memory usage reports.
The only definitive evidence is whether you see an OutOfMemoryError or not. Until you see one, there is no *proof *of a memory leak. To get a real sense of required memory, re-run the test with smaller and smaller maximum heap size until you see an OutOfMemoryError. Then you'll know :-) -Archie On Tue, Feb 10, 2009 at 3:21 AM, massimo citterio <[email protected]> wrote: > Hi to all, > I'm trying to investigate on a high memory usage, by an svg application > I made. > I've split the components into mini test cases, and I'm profiling each > of them. > What I find very strange is that a very simple svg application > (described below) ranges from 30Mb to 186Mb, and what's worse, for a > very long time (half the test time, 5h) the oscillations are very high. > see the chart: > http://img19.imageshack.us/my.php?image=pesosvg2he9.png > > Is this the expected behaviour? -- Archie L. Cobbs
