Hello,

An application (Windows Service) registers and adds all objects to the
container upon startup.  All dependencies are handled through
constructor injection, nowhere in the application (other than startup)
is container.resolve used.  The problem we're having with this
application is that it has a high memory footprint (~75MB) and does
not release memory well, growing to 500MB+ in a short amount of time.
What would you suggest is a good approach to go about fixing the
issue?  The Service is usually in a dormant state until it is
"triggered".  I've considered more of a resolve/release of objects
during it's active state.

Thanks.

-- 
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.

Reply via email to