Hi Tomek
Thanks for the advise. I'd like to start by saying that I identified
the memory issue and it was not Monorail or Windsor.
I did use dotTrace Memory to investigate the memory issue, but there
was no evidense of a traditional memory leak.
After eliminating code and rebuilding the solution from the ground up,
I identified the issue as .Net's XmlSerializer and a third party tool
called AutoMapper.
The issue with XmlSerializer is document by Microsoft at these two
links:
http://blogs.msdn.com/b/tess/archive/2006/02/15/532804.aspx
http://support.microsoft.com/kb/886385/en-us
I never isolated the root cause of the memory issue with AutoMapper.
We only used it in a few places, so it was easier to remove our
dependency on the tool than to investigate whether it could be used
without leaks.
Thanks
Sean
--
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.
