I've tested warp-persist v2 with Guice v2 with guice.custom.loader=true
and the leak is still there. I've spent a couple of hours trying to
track it down but it seems I don't know what I'm doing. It's not obvious
to me how to use the Netbeans profiler or JVisualVM to track this down.
I tried deploying and undeploying my webapp twice and comparing the two
memory snapshots. That got me nowhere. Now I'm thinking I'll deploy and
undeploy my webapp, take a snapshot and investigate why Guice is still
in memory (since it shouldn't be).
Gili
[EMAIL PROTECTED] wrote:
> I believe the FinalizableReferenceQueue leak might also pose problems.
> This will be fixed soon...
>
> http://code.google.com/p/google-guice/issues/detail?id=227
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
