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 there is a working patch for 235, but it has not yet been committed to confirm this you could try running with the "guice.custom.loader" system property set to "true", which will re-enable the unloading of proxy classes. as for threadlocals, there is only one in the core code and it should get cleaned up when the context stack completes - but again, this could be related to the proxy classes (depending which version they're using) I will post a similar messages in the warp-persist mailing list. > > Thanks, > Gili > > > -- 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 -~----------~----~----~----~------~----~------~--~---
