One last thing to add I resolve presenters like this:
public TPresenter ResolvePresenter<TPresenter, TView>(TView view) {
return this.container.Resolve<TPresenter>(new {view = view});
}
Then in my aspx (view) page:
this.presenter = Factory.Instance.ResolvePresenter<MyPresenter, IMyView>(this);
Could this be the cause of the leak here because of injecting the view
into the presenter where the view implements IDisposable?
Cheers
On Tue, Nov 4, 2008 at 3:41 PM, Stefan Sedich <[EMAIL PROTECTED]> wrote:
> To add to this my presenters which are resolved do not implement
> IDisposable so should they have a reference held to them?
>
>
> Cheers
>
> On Tue, Nov 4, 2008 at 3:37 PM, codemonkey <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> I have a web app using Windsor, I did no have NoTrackingReleasePolicy
>> set at the ReleasePolicy and ran a load test, memory leaked like bad.
>> I set this to the ReleasePolicy and all is rosy no leaks at all, what
>> is Windsor doing without this policy that causes this?
>>
>> Should I be releasing my presenters or just use this policy as I no
>> have no leaks.
>>
>>
>>
>> Thanks
>> >>
>>
>
>
>
> --
> Stefan Sedich
> Software Developer
> http://weblogs.asp.net/stefansedich
>
--
Stefan Sedich
Software Developer
http://weblogs.asp.net/stefansedich
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
