2008/11/27 Gili Tzabari <[EMAIL PROTECTED]>
>
> Stuart McCulloch wrote:
> > so it's not a matter of what's keeping the Finalizer alive - you need to
> > find out what's
> > keeping the Guice classloader alive, as this is keeping the Finalizer
> > alive indirectly
>
> By "Guice classloader" you mean the CL used to invoke
> Guice.createInjector?
>
it depends how you're deploying it - if you're using a WAR then that should
be the one
Is System.setProperty("guice.custom.loader", "true") supposed to make
> a
> difference?
>
the patched guice jar I'm using has this enabled by default, but this is
more about eager unloading of proxy classes
> > you should instead look for any references from outside of the Guice
> > classloader,
> > that might be keeping the classloader alive - you should also try to run
> > finalization
> > and GC a few times just to make sure everything has been cleared +
> collected
>
> That's hard. If I understand you correctly then the guice
> classloader
> is actually the container ClassLoader and when I right-click on that and
> say "find GC root" it finds the first/closest root which is the
> Finalizer thread :(
>
> I just put my heap dump online for your review (6MB download):
> http://bbs.darktech.org/guice-leak.rar
>
> > have you tried creating a small testcase? (ie. Guice + small client, no
> > use of warp)
> > then if the leak is still there then feel free to email me that testcase
> > + instructions
>
> If all else fails that's what I'll do ;)
>
ok - otherwise I'll try to put together a simple example later today when I
have time
> 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
-~----------~----~----~----~------~----~------~--~---
