Hi there, do you have any ideas concerning this matter? Since you can quickly lose a lot of memory this way.
Could it be a DOM parser problem (removing nodes without removing its children first)? Or is it a Java garbage collection problem (but I do not think that I keep any references to nodes below the node to be removed)? TIA, Martin B.t.w. Does Java 1.4.1 (Windows 2000) introduce any problems? Squiggle locks up every now and then when I try to open a new file after installing JDK1.4.1. > -----Original Message----- > From: Barbisch, Martin > Sent: Donnerstag, 10. Oktober 2002 11:52 > To: '[EMAIL PROTECTED]' > Subject: Losing memory when using removeChild() > > > Hello Batik users, > > a few weeks ago (August 28th 2002) James McArthur wrote about > a memory leak, > when modifying the contents of the SVG tree. > I am experiencing (almost) the same problem, and therefore my > question is: > > Suppose that I have (e.g.) a <text> node which contains some > <tspan> nodes. > Now I want to remove the text node. Is it necessary to remove > all of the > children (i.e. the tspans) first, or may I safely just remove > the text node? > And what if I have a very deep hierarchy of nested <g> nodes? > > I always thought that removing a node would also free the > memory used by all > its children. But now I am not that sure about this anymore... > > > Any help appreciated. Cheers, > > Martin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
