Exception of type System.OutOfMem oryException was thrown.

[Daniel]

Exception of type System.OutOfMem oryException was thrown.

this error is occuring when on arbitrary threads in my .net windows service.
There is 2 gigs of memory on the machine and this .net windows service only
uses 50 megabytes. What could be causing this? how to fix?

[Stoitcho Goutsev \(100\)]

Daniel,

I've seen OutOfMemory exceptions thrown when the problem is completely
different. For example Graphics.DrawLi ne throws this exception and obviously
there is no memory issue. I'd suggest to debug the code and find out what
the real reason for that might be.
"Daniel" <so************ *******@yahoo.c om> wrote in message
news:Os******** ******@TK2MSFTN GP10.phx.gbl...

Exception of type System.OutOfMem oryException was thrown.

this error is occuring when on arbitrary threads in my .net windows
service.
There is 2 gigs of memory on the machine and this .net windows service
only
uses 50 megabytes. What could be causing this? how to fix?

[Crash]

You can run out of memory if your application is not releasing pinned
memory blocks because the garbage collector only frees memory up to the
first pinned block. Aka if your application pins some memory, then
allocates heap space, then pins more memory, then allocates more heap
space - eventually you will have memory issues because the last pinned
block will "slide" down the heap leaving less and less free space to a
point where an allocation request fails...

You can check your heap usage with perfmon and the .NET memory & GC
performance counters; this will tell you if the out of memory exception
is a red herring or not. If it is a real out of memory condition then
you can use CLRProfiler {free download from msdn website} to see heap
usage in detail...

Also, if it is a real out of memory condition, then in code you might
look for:

- Assure that any class that implements the IDisposable interface is
wrapped in a "using" statement block or else is explicitly disposed in
a finally block

- Assure that pinned {fixed in C#} objects are going out of scope in a
timely manner

- For v1.x of .NET, assure that any COM Interop RCW classes are
explicitly freed with Marshal.Release COMObject()

[Willy Denoyette [MVP]]

"Crash" <so*********@sa n.rr.com> wrote in message
news:11******** *************@t 39g2000cwt.goog legroups.com...
|
| You can run out of memory if your application is not releasing pinned
| memory blocks because the garbage collector only frees memory up to the
| first pinned block. Aka if your application pins some memory, then
| allocates heap space, then pins more memory, then allocates more heap
| space - eventually you will have memory issues because the last pinned
| block will "slide" down the heap leaving less and less free space to a
| point where an allocation request fails...
|

Not true, pinning only prevents compactation of the heaps (managed) that
means that memory consumption grows while large blocks of the heap aren't
used to contain live objects, but the memory consumption grows! which is not
the case here (50MB used).

Willy.

[Willy Denoyette [MVP]]

"Daniel" <so************ *******@yahoo.c om> wrote in message
news:Os******** ******@TK2MSFTN GP10.phx.gbl...
| Exception of type System.OutOfMem oryException was thrown.
|
| this error is occuring when on arbitrary threads in my .net windows
service.
| There is 2 gigs of memory on the machine and this .net windows service
only
| uses 50 megabytes. What could be causing this? how to fix?
|
|

Please be more specific - What memory? How did you measure, what are you
doing in this Service, you aren't using System.Drawing namespace classes do
you?

Willy.