No, RhinoContainer will use the same approach as Windsor, so adding NoTracking policy should solve that as well.
On Mon, Dec 22, 2008 at 1:11 PM, [email protected] < [email protected]> wrote: > > Hi, > > Setup: > Latest Castle, NHibernate and Rhino trunk. > Using UnitOfWorkApplication > Configuration: Windsor.boo > View Engine: Brail > > > Problem: > Last week we appeared to be suffering a memory leak on a new site we > are developing. We initially thought the leak was caused by > ViewComponents. We thought this because the leaks did not occur when > we removed all components from our brail. However having spoken to > the Castle group they asked questions about whether or not the > components were being released which pointed me to take a look at the > RhinoContainer. > > In the end I went with Victor Kornov's method to stop leaks. > > http://weblogs.asp.net/stefansedich/archive/2008/11/05/avoid-memory-leaks-when-using-windsor-and-not-releasing-objects.aspx > > How valid is this as a solution? Does the RhinoContainer > automatically release components? > > John > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
