>
> from FileData.java
>
> protected void finalize() throws Throwable
> {
> name.delete();
> super.finalize();
> }
>
> so that looks ok (I think forgetting to call the superclass in a finalize
> can result in an actual leak can't it?) (Maybe we should reverse those
> calls or at least catch IOExceptions on the file delete...)
I don't think so. The API docs dont say that any super call is necessary.
>
> I noticed that the corresponding class for the storable fields,
> FileDataProperties lacks a finalizer. Of course, that should be a harddisk
> leak, not a memory leak.
>
> Somebody said that the StreamStore is not working, so that could be a
> likely candidate as well (broken things tend to break in many ways).
True.
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
