I don´t believe this is correct. The OutOfMemoryException *does* indicate
that the process is out of memory, or at least that it cannot satisfy a
memory request, either because all available memory has been assigned or the
memory manager cannot find a block large enough to fulfill the request,
usually due to fragmentation. But this will not necessarily cause the
process to be recycled or is related to the memory limit in machine.config.
For example, this can be verified by placing the following code in the
handler for a button in a web form.
protected void Button1_Click ( object sender, EventArgs e )
{
byte [ ] buffer = new byte[ int.MaxValue ];
}
This will attempt to allocate a very large array of bytes which cannot be
satisfied, and will therefore throw an OutOfMemoryException, but the process
will not be recycled. This can be verified by monitoring the worker process
restarts performance monitor counter, or by checking the ProcessInfo history
(see System.Web.ProcessModelInfo.GetHistory( )).
As you mention, the memoryLimit parameter in the <processModel> section of
machine.config in the case of IIS5, or the memory recycling properties for
the application pool in IIS6, indicate a threshold which, if exceeded, will
cause the process to be recycled. This will occur even if there's still
memory available to allocate and does not cause an OutOfMemoryException. All
the requests which are currently executing when the memory limit is reached
should be processed normally by the terminating process, while any new
requests are handled by a new worker process.
Fernando Tubio
----- Original Message -----
From: "Mark Kucera" <***@INTERCERVE.COM>
To: <DOTNET-***@DISCUSS.DEVELOP.COM>
Sent: Wednesday, January 17, 2007 10:39 AM
Subject: Re: [DOTNET-WEB] exception with no details
Or in apps that run a query that returns a gigantic amount of
information, say a report that allows entry of a date range that the
user leaves blank. Something to note is that this error doesn't
indicate that the server was completely out of memory. ASP.NET defines
a threshold % (in machine.config) and when that % of consumed then it
will throw the out of memory exception. In theory when this exception
is thrown, the app should unload and all the memory s/b reclaimed. In
1.1 this didn't happen and users generally continue to get out of memory
errors. Which version of ASP.NET are you using?
Mark
-----Original Message-----
From: Discussion of building .NET applications targeted for the Web
[mailto:DOTNET-***@DISCUSS.DEVELOP.COM] On Behalf Of Peter Osucha
Sent: Wednesday, January 17, 2007 8:17 AM
To: DOTNET-***@DISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-WEB] exception with no details
Where I've seen that error most often is from infinite loops of one kind
or
another. Don't know why the stack and target are empty though...
> -----Original Message-----
> From: Discussion of building .NET applications targeted for
> the Web [mailto:DOTNET-***@DISCUSS.DEVELOP.COM] On Behalf Of Jeff
> Sent: Monday, January 15, 2007 3:00 PM
> To: DOTNET-***@DISCUSS.DEVELOP.COM
> Subject: [DOTNET-WEB] exception with no details
>
> keep getting this on one of our apps. Anyone know how to
> troubleshoot this, or why the 3 properties are empty. We have
> an err processor the sends us the details, but the there is
> not much there to work with. Have not been able to reproduce
> this in our testing yet. Thanks.
>
>
>
> Message: Exception of type System.OutOfMemoryException was thrown.
>
> Source:
>
> Stack Trace:
>
> Target Site:
===================================
This list is hosted by DevelopMentor(r) http://www.develop.com
View archives and manage your subscription(s) at
http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com