On 6 Aug 2012, at 19:56, Brian Pontarelli wrote: > Bump. Any ideas on why this is happening and how to fix it? It seems like a > pretty bad memory leak in Guice that could impact GC on high scale > applications.
Just took a quick look and there seem to be two places that may hold onto error objects: The constructor cache in ConstructorInjectorStore An anonymous class in TypeConverterBindingProcessor The actual number of objects depends on your application - I just instrumented a multi-injector system with hundreds of bindings in total and found 33 Errors objects retaining ~4k of heap. Note that this is not a leak per se, in that it should not increase over the time of your application and will eventually get moved into the old space, but it is an overhead that could be reduced. I'll see if I can dig further... > -bp > > On Jul 28, 2012, at 2:57 PM, glenviewjeff <[email protected]> wrote: > >> This sounds a lot like my post about irrelevant in memory errors on android >> from a few days ago... -- 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.
