Your code should include a call to container.Release

That being said, the burden impl should be optimized to only hold a
chain (and references) if somewhere in the graph there's a disposable
type, which is something I'm planning to add.



On Mon, Dec 22, 2008 at 11:16 AM, Germán Schuager <gschua...@gmail.com> wrote:
>
> Don't know if this is the case, but I've noticed that after the
> component burden implementation the container doesn't release
> references to transient components:
>
> http://support.castleproject.org/projects/IOC/issues/view/IOC-ISSUE-132
>
> On Dec 22, 4:01 pm, hammett <hamm...@gmail.com> wrote:
>> I bet the problem lies on the new implementation for the burden stuff.
>> Will try to fix it during the holidays.
>>
>> On Mon, Dec 22, 2008 at 2:56 AM, johnpoll...@googlemail.com
>>
>>
>>
>> <johnpoll...@googlemail.com> wrote:
>>
>> > I took Victor's advice and added the NoTrackingReleasePolicy which
>> > appears to have fixed the memory leak.  I may well post the issue on
>> > the Rhino group and see what they say.  It seems linked to the
>> > UnitOfWorkApplication.
>>
>> > On Dec 19, 4:56 pm, "Victor Kornov" <wee...@gmail.com> wrote:
>> >>http://weblogs.asp.net/stefansedich/archive/2008/11/05/avoid-memory-l...
>>
>> >> On Fri, Dec 19, 2008 at 7:51 PM, johnpoll...@googlemail.com <
>>
>> >> johnpoll...@googlemail.com> wrote:
>>
>> >> > Sorry forgot to add about Windsor.  Yes we are using Windsor
>> >> > integration.
>>
>> --
>> Cheers,
>> hammetthttp://hammett.castleproject.org/
> >
>



-- 
Cheers,
hammett
http://hammett.castleproject.org/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to castle-project-users@googlegroups.com
To unsubscribe from this group, send email to 
castle-project-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to