Comment #40 on issue 288 by [email protected]: FinalizableReferenceQueue still leaks
http://code.google.com/p/google-guice/issues/detail?id=288
I must be missing something--does it make sense to have a custom executor? How does this solve the sticky references that prevents gc of the frq?
Using "NONE" solves it, but is there a way to have the Finalizer thread and still have the container not leak?
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" 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-dev?hl=en.
