Subject Re: Memory Leak in client-java - FIXED!
Author Roman Rokytskyy

> With those latest changes to the CVS, is that memory leak taken care
> of? I saw that you removed a whole hunk of statement tracking code
> in but since I changed something in
> (the missing remove call) I was
> wondering if this fixing this issue on another end or if you haven't
> been able yet to integrate the fix.

That method you were talking above was never called (at lease that's
what my JBuilder told be). I sent an email to David Jencks asking to
check it.

Memory leaks should be fixed for now, because the only reference on
the statement handle has instance of FBStatement, and it is only
referenced by FBConnection. All references are cleared on close.

Can you check your memory tests?