Archie Cobbs wrote:
Note that one thing my application does is change the "xlink:href" attribute on existing <use> nodes to point them at different symbols.
Perhaps there is some leak where Batik retains a reference to the previously pointed-to <use> referent?
Aha! I changed my code to delete the previous <use> and add a new <use> each time, instead of just changing the "xlink:href" attribute, and this fixed the leak.
So as far as I can tell there is a Batik memory leak in handling this case.
What version of Batik are you using?
Also are the href references local, "#blah", or external, "foo.svg#bar"? A mix?
I've given the code a good looking over and it is hard for me to see where the leak occurs, but I am very interested in finding it. Any chance of a reproducible test case?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
