Hello !
I use Batik in a Java application and have a Out of Memory error after
opening and closing several times big XML files. I first thought the
memory leak was due to my code, but I now think it is coming from Batik
(not a 1.6 regression, because I had these Out of Memory errors before 1.6).
I used Netbeans with the memory profiler with the batik built-in SVG
browser application (1.6 version), opening several times the "anne.svg"
SVG file, and the profiler shows that the "live" objects are increasing
for these classes, after each new opening :
- org.apache.batik.dom.GenericText
- org.apache.batik.dom.GenericAttr
- org.apache.batik.dom.AbstractElement.Entry
- org.apache.batik.dom.AbstractParentNode.ChildNodes
- org.apache.batik.dom.svg.SVGOMGElement
- org.apache.batik.dom.svg.SVGOMPathElement
- org.apache.batik.gvt.ShapeNode
- org.apache.batik.gvt.CompositeGraphicsNode
- org.apache.batik.gvt.event.GraphicsNodeChangeEvent
- org.apache.batik.ext.awt.geom.ExtendedGeneralPath
- org.apache.batik.dom.util.DocumentDescriptor.Entry
There is always one unique org.apache.batik.dom.svg.SVGOMDocument (same
for org.apache.batik.dom.svg.SVGOMDefsElement, for example), so I think
this is not coming from caching each previously opened SVG Documents.
I don't use the browser in my application, but I have the same results,
so I think this is not coming from the browser itself...
Anyone has a hint on the reason of these memory leaks ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
