2008/10/28 Dhanji R. Prasanna <[EMAIL PROTECTED]> > > On Tue, Oct 28, 2008 at 2:35 PM, Stuart McCulloch <[EMAIL PROTECTED]>wrote: > >> 2008/10/28 Gili <[EMAIL PROTECTED]> >> >>> >>> Hi guys, >>> >>> I would appreciate your help commenting on this issue: >>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=5104 >>> >>> The Glassfish guys have identified two memory leaks, one of which >>> results from Guice's use of thread-local storage. They're asking >>> questions about the Guice codebase. You know a lot more about this >>> code than I do so I would appreciate your feedback :) >>> >> >> firstly, which version of guice is being used? >> >> secondly, I would fully expect the current trunk to leak classes on a >> restart >> because the code to allow unloading of proxies is currently disabled due >> to issue http://code.google.com/p/google-guice/issues/detail?id=235 >> > > It shouldn't matter, the webapp classloader itself should be gc'ed away. > This is some other leak, maybe thru Hibernate or commons-logging. >
maybe, but enabling that option would reduce the "noise" from the proxy classes and help them find the true cause, especially if they're doing leak analysis of the Java heap... Dhanji. > -- Cheers, Stuart --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
