You should definitely try some detailed memory profiling. JetBrains dotTrace has a great tool (dotMemory or sth like that). Grab evaluation from their website a you will be able to see where your memory leaks grouped by namespaces, classes or threads with stack traces. This should give an idea where exactly in your code there is a problem.
Report back if you try that. Regards Tomasz -- 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.
