Transient lifestyles introducing memory leak?

TheSachin / sutekishop

Automatically exported from code.google.com/p/sutekishop

0 stars 0 forks source link

http://stw.castleproject.org/Default.aspx?Page=LifeStyles&NS=Windsor&AspxAutoDet
ectCookieSupport=1

Transient components are tracked by the container
To ensure proper components lifecycle management Windsor will track your 
components, even transient ones. That means that unless you release them, 
Garbage Collector will not be able to reclaim them, and you'll end up with 
de-facto memory leak. Remember to release your transient components. 

You use transient on a lot of your interfaces and I don't see any calls to 
release.  Is this a problem?

Original issue reported on code.google.com by steve.go...@gmail.com on 24 Nov 2010 at 11:27

Hi Steve, No, it's not a problem. The root 'resolve' call of each request's dependency graph occurs in the MvcContrib WindsorControllerFactory. this calls release on the controller at the end of the request. Windsor traces the dependency graph and releases all the transient components.

TheSachin / sutekishop

Transient lifestyles introducing memory leak? #32