this explains the problem you were facing: http://davybrion.com/blog/2008/12/the-component-burden/
On Tue, Jan 6, 2009 at 3:03 PM, Erez <[email protected]> wrote: > > Hi everyone, > > We have been using a version of Castle from November 2007, and so far > it has worked great for us. We run now into some resource leak issues, > and suspected Castle is to be blamed ... we took now the last build, > and it looks like our problems are over. I wanted to ask if: > a. can anyone confirm such problems indeed where fixed the last year ? > b. if there's a single patch I can take for this fix, instead of just > move to the newest build, I think I would prefer that > c. if not, is there a point in time the last few months I can take a > version which is more "safe" than just yesterday's build ? Is there a > list somewhere of all MAJOR changes since November of 2007 which I can > go over and understand the impact for me of doing this upgrade ? > > Thanks in advanced .. > > and now, for the problem descreption: > > Object T with transient lifestyle. > Object C, which is an IDisposable, with a custom lifestyle > Object C is a dependency of T > > T is resolved, and then C. When C is created, it has some > LifecycleStep configured. Meaning that it will be disposed. > > We call Kernel.release(C) but the object is not disposed. When C is > not a dependency (it is resolved directly), it is released by that > same call correctly. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
