Gar! Nevermind. I missed setting my ViewComponents to transient when registering them. I'm going to set that straight and profile again.
From: [email protected] [mailto:[email protected]] On Behalf Of Tyler Burd Sent: Thursday, September 17, 2009 4:05 PM To: [email protected] Subject: LifeCycleComponentReleasePolicy and memory with monorail Hi all, sorry to keep clogging the list. While profiling my monorail application, I noticed that the LifeCycleComponentReleasePolicy was keeping hold of any ViewComponents and runtime-generated brail view instances. I let the app sit for a while and those instances were never reclaimed. Is there something I need to do to ensure that container.Release is called for those special types? I am using a version of the trunk that is about 3 weeks old. What I've done to temporarily get around this is create this custom release policy: public class CustomReleasePolicy : LifecycledComponentsReleasePolicy { public override void Track(object instance, Burden burden) { if (instance is Controller || instance is ViewComponent || instance is Filter || instance is BrailBase) return; base.Track(instance, burden); } } --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
