Michael Sinz wrote:
> Actually, this code is a "problem" but the bug is in the test.
> Why? Well, you are never returning from the constructor and thus
> certain parts of the system are still locked (synchronized) which
> prevents some forms of GC.
>
thanks for the comments on synchronization on the constructor, that is
useful to know....
>
> Generally, one does not want to do all the work in a constructor :-)
>
yup ! :-)
I tried the variation you suggested and am still having the same problem -
the process slowly grows in size...
Crispin
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
