.Net OutOfMemory on Server but not Desktop
- by Jörg Battermann
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?