We have a project that adds up to 125 NH mappings at run-time. Each time we add a mapping, we regenerate our session factory, as follows:
ourConfiguration.AddXml(mapping); ourSessionFactory = ourConfiguration.BuildSessionFactory(); After loading all the mappings (and nothing else), the process consumes over 3GB of RAM (on a 64-bit OS). By comparison, if I load all the mappings at application startup, the process consumes just a few 100MB. Is there something about calling AddXml() and then BuildSessionFactory() repeatedly that would cause a memory leak like this? Is NHibernate holding on to all the old session factories, for example? If so, is there some way to release them? Thanks. -- Brian -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
