.Net OutOfMemory on Server but not Desktop
Posted
by Jörg Battermann
on Stack Overflow
See other posts from Stack Overflow
or by Jörg Battermann
Published on 2010-05-07T14:55:33Z
Indexed on
2010/05/07
15:18 UTC
Read the original article
Hit count: 283
Is it possible that the .Net framework behaves differently when it comes to garbage collection / memory limitations on server environments? I am running explicitly x86 compiled apps on a 64bit server machine with 32gbs of physical ram and I am running out of memory (SystemOutOfMemoryException) even though nothing but that particular app is running and the server/all other apps utilize 520mb total.. but I cannot reproduce that behaviour on my own (client win7) machine.
Now I know that the app -is- memory intensive, but why is it causing problems on the server and not on the client?
© Stack Overflow or respective owner