Hi Pepping, "Pepping, Florian" <[EMAIL PROTECTED]> wrote on 12/19/2006 07:38:22 AM:
> once again a problem using batik: > I have a JSVGCanvas and often load another SVG with canvas. > setURI(svgFile.toURL().toString()); into it. The consequence is a > more or less heavy memory-leak, whatever Batik-Version I use. The > following observations can I report: [...] > It seems that the memory level settles down after a longer time > (half an hour), however batik than uses more than 100MB or more > of memory. Perhaps you can have a look at this behavior. This doesn't sound like a problem. This is just how Garbage Collection works. In Java you don't delete/free memory, the JVM automatically detects memory that is no longer referenced and free's it for you. However this detection can be time consuming so it generally doesn't look for work until memory is almost full. So if memory consumption is settling then there isn't a memory leak.
