What's the reason for the committed memory increasing?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Justin Yoke - 05 Feb 2004 02:21 GMT

I made a distributed system in VB.Net for my company. About 80 clients are connecting to the server through leased line every day. I have to restart the server computer every one week, otherwise, the memory will be exhuasted.

I'm trying to figure out what reason it is. It is the problem in my program to release the resource or the problem in Windows self. There are really some errors happening in socket communicating from my server to client or client to my server. Does this result in the above memory exhuasting problem

Appreciated any helps.

Reply to this Message

Jim P. - 25 Feb 2004 06:16 GMT

I am also experiencing this problem. Each new socket connection adds 4k of
memory usage that the machine never gets back.

I am using Socket.Close(). But I'm using Asyncronous calls to get the data.
I close the socket in the final StateObject that holds my socket but is the
origional socket staying connected?

How do we make sure that each instance of the socket is closed and
distroyed?

thanks,
Jim

> I made a distributed system in VB.Net for my company. About 80 clients are connecting to the server through leased line every day. I have to restart

the server computer every one week, otherwise, the memory will be exhuasted.

> I'm trying to figure out what reason it is. It is the problem in my program to release the resource or the problem in Windows self. There are

really some errors happening in socket communicating from my server to
client or client to my server. Does this result in the above memory
exhuasting problem?

> Appreciated any helps.

Reply to this Message

What's the reason for the committed memory increasing?

Free Magazines