http://blogs.msdn.com/tess/archive/2008/02/22/reader-email-private-bytes-remain-higher-than-expected.aspxI got this question today (through the blog) and normally I don't really answer questions sent to me directly through the blog for a couple of reasons already mentioned in the Contacting Tess... post, mostly because I don't have the time to answer allsv-SECommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/tess/archive/2008/02/22/reader-email-private-bytes-remain-higher-than-expected.aspx#7850112Fri, 22 Feb 2008 21:36:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:7850112Lee Culver<P>I've seen a situation where the XSLT files, over time, get compiled with Reflection.Emit (if I remember correctly), and are never collected (as Ref.Emit libraries are never collected). &nbsp;XSLT or other compiled scripts would explain the high number of assemblies, and if the number doesn't go up while the memory usage doesn't go up, then it makes sense that this would be your issue...</P>http://blogs.msdn.com/tess/archive/2008/02/22/reader-email-private-bytes-remain-higher-than-expected.aspx#7851124Sat, 23 Feb 2008 00:24:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:7851124Tim Donovan<p>Thanks for the reply! &nbsp;I believe I fall into the 2nd scenario. &nbsp; &nbsp;I have multiple applications running in the process so I think that is why the assembly count is high. &nbsp;I also have caching turned on. &nbsp; I don't do any XSLT stuff so that isn't it. &nbsp;Working on testing my windbg chops right now to get a dump and analyze that. &nbsp;</p>