Comment #4 on issue 756 by jim.hu...@gmail.com: Memory leak by using child
injector and multibinder
http://code.google.com/p/google-guice/issues/detail?id=756
What are the chances of getting the memory leak fix in to Guice 4.0?
We've heavily tested the patch submitted in Comment #3 in our internal
application and it works perfectly and with no unintended consequences. We
would rather not maintain an internal fork of Guice, so it would be
fantastic if we could get the fix into Guice 4.0.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-guice-dev+unsubscr...@googlegroups.com.
To post to this group, send email to google-guice-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/google-guice-dev.
For more options, visit https://groups.google.com/d/optout.
