Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 05, 2010 04:28 PM by smhetar
Nov 05, 2010 04:28 PM|LINK
My web application is in Classic ASP and in that we had developed few modules in ASP.Net 2.0.
Initially all modules were working fine but as we goes on developing new modules in ASP.Net 2.0 we are getting this error very frequently - Exception of type 'System.OutOfMemoryException'.
[OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.]
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141
System.Reflection.Assembly.Load(String assemblyString) +25
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32
Reseting the IIS can resolve this issue temporarily but we need the reasons and fixed solutions for this memory issue as we have enough memory on the Server.
Is there any way to handle classic asp and asp.net worker process to allocate some fix memory in order to avoid memory conflicts?