James, Seems like it's just you and me. :-) I found a workaround, which is to call loadSVGDocument() rather than setSVGDocument(). This apparently does not cause the leak.
James McArthur wrote: > Hi, > > I was beginning to think I was the only one with the problem here :) > > I have tested the same code that I posted earlier with 1.5b3 and 1.5b4b > and the problem is still there... > > James > > On Fri, 2002-09-20 at 01:32, George Armhold wrote: > >>Hi, >> >>I'm experiencing a similar problem to the one that James mentioned >>back in August, but I'm using Batik 1.5b4. In my case, I'm using a >>JSVGComponent and asking it to successively load different SVG >>documents by calling setSVGDocument(). Windows Task Manager shows the >>memory going up and up with each successive document, until finally I >>get an OutOfMemoryException. I can provide a sample program that >>tickles it, if needed. Can anyone suggest a fix or workaround? >> >>Thanks -- George Armhold Rutgers University eLearning Grant, DCIS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
