Sorry to bother you personally. I've not seen messages about memory leaks often, and I'm now wondering why they would appear with Java being specifically designed against this possibility. Is it a JVM defect? Is there a way to fool GC? Or is it simply a problem with collection contents clean-up (i.e. there's data being stored in a list that gets stale and not deleted)? Probably the third, I'd guess... :)
I'm a Java newbie (still, after a year and a half of studying it), so don't bother with long explanations. TIA, Doc > -----Original Message----- > From: Zlatin Balevsky [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 21, 2003 8:43 PM > To: [EMAIL PROTECTED] > Subject: [freenet-dev] target uptime > > > My node deadlocked after 15 hrs of uptime in a > particularily-hard-to-debug deadlock. We are also still > leaking memory, > only very slowly. To debug these issues we'll need a _LOT_ of time. > > Its a lot more practical to decide on a target uptime which > will be Good > Enough (tm) for a 0.5.2 release. We could decide on > something like 2, 5 > or 10 days (even biggest ubernodes rarely last beyond 10 days w/o > restart). Then set up as many nodes as possible simultaneously > (coordinated through irc) and if they are all alive after the decided > period we stamp the code as Good Enough(tm). > > _______________________________________________ > devl mailing list > [EMAIL PROTECTED] > http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl > _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
