Hi Ryan,
"Ryan.Wilson" <[EMAIL PROTECTED]> wrote on 09/19/2008 02:14:02
PM:
> According to JProbe, most of the stuff left on the heap are objects like
> GenericText, GenericElementNS, and SVGOM*Element, etc. From what I've
> traced, almost all of them have a link back to a BridgeContext object
that
> is sitting around. I, for the life of me, cannot figure out why it is
still
> around.
I'm a little confused about how anything sticks around between
viewings of the Japplet. Also won't JProbe tell you what the
live object chain is from a root to the BridgeContext? If the
BridgeContext is live it will keep lots of other stuff live.
However to answer you question:
> Ryan.Wilson wrote:
> > 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.
In our memory leak test we do the following:
theFrame.remove(theCanvas);
theCanvas.dispose();
theFrame.dispose();
theFrame=null;
theCanvas=null;
