Eamonn O'Connell
10/7/2004 9:39:00 AM
We are experiencing what appears to be a memory leak in .net Remoting. We are
using Remoting to connect our ASP.net web app on one server to our business
logic (class libraries) on another ("app") server. We created a Windows
service which runs on the "app" server, which listens for the remoted calls,
and calls the correct business rules procedure in our DLL.
After several hours of use, the Virtual Memory being "used" by our remoting
service continues to grow to a point where Windows has to resize the v.m.
paging file and in doing so denies some memory requests. This results in
clients getting "Out of Memory" errors!! Only then does the Garbage Collector
do its job, and the memory being used by our remoting service drops way
off...to a fraction of what it was.
Why is the Garbage Collector not clearing the memory before Windows needs to
resize the v.m. file.
Does remoting have memory leaks?
Is the GC prevented from running as there is not enough memory for it to run?
We are using Windows 2000 Server with 256 MB RAM, .net framework 1.1, VB.net.
V.M. min size = 192mb, max size = 384mb.