Thanks for the tip, but it seems about the same.  I'm using Netbeans 5.0
with the profiler plug-in and INSANE to monitor the heap.  Garbage
collection is great with a static canvas, but when the canvas is switched to
dynamic, garbage collection seems to break down.  I'm loading some pretty
big svg files(building cad) that are around 2.5Mb.  My understanding of gc
could be better, but something doesn't seems right if the problem goes away
by commenting out one line of code
(canvas.setDocumentState(JSVGCanvas.ALWAYS_DYNAMIC)).

-----Original Message-----
From: David Avery [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 2:57 PM
To: [email protected]
Subject: Re: Memory & Dynamic Canvas



Try
canvas.flush();
canvas.flushImageCache();

in your dispose code.

Greg Steele wrote:
> Hi,
> I've been trying to track down a major memory leak in my app.  After
> creating a very simple test app, I was able to determine that setting
> canvas.setDocumentState(JSVGCanvas.ALWAYS_DYNAMIC) was somehow causing
> unused objects to remain on the heap after I removed the canvas from the
> container.  The memory leak goes away when I leave the canvas static; I
can
> close and reopen the same SVG doc indefinitely.
>
> Perhaps, I'm not closing the canvas correctly?  Currently, I just remove
it
> from its parent container.
>
> Unfortunetly, I need the canvas dynamic.  Forgive me if this has been
> addresses elsewhere, but I scoured the mailing list for a fix.
>
> Thanks,
> Greg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


--
David Avery
Front Gate Tickets
1711 South Congress Austin, TX 78704
Ph: 512-674-9364




---------------------------------------------------------------------
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]

Reply via email to