I am using batik to display and manipulate an SVG document in a Japplet. A memory leak is occuring such that if the applet is viewed more than once or twice without having closed the browser, a outofmemory error is thrown.
I have viewed a number of heap dumps of the applet between viewings and when it has crashed and Batik appears to be the culprit. I have searched through the mailing list and the docs and nothing I found helped with the problem. My question at the moment is what form of cleanup should be performed on batik during the destroy method of an applet? I have some code implemented already, but it is possible I am missing something. Regards, Ryan Wilson -- View this message in context: http://www.nabble.com/Batik-Memory-Leak-in-Applet-tp19536209p19536209.html Sent from the Batik - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
