Remoting memory leak?

  • Thread starter Thread starter Yair
  • Start date Start date
Y

Yair

Hi,
After executing a server-client remoting scheme I wrote,
I've noticed a constant memory growth (both at the server,
and at the client). Searching through various newsgroups,
I've stumbled across various posts, regarding this
behaviour.
My question is: Is there currently any known bug,
regarding Dotnet 1.1, which can lead to such behaviour? We
have spent a significant amount of time on the subject,
and ruled out the possibility of having
something "holding" references to our own objects.
Thank you very much for your time.
 
Hi,
what kind of activation do you use?
If the remoting object is client-activated:
- Do you override InitializeLifetimeService?
- Does your client implement ISponsor interface?

Dmitry.
 
Hi,
Thank you for your reply.

Our remoting object is server-activated (singleton). So, a
single remoting object should handle all of our remoting
calls.
Also, we override 'InitializeLifetimeService' and force a
null return - so the lifetime of the remoting object
should be infinite.
Checking the client process, we noticed that numerous
threads are being opened by the framework, and running
NetStat at the background, showed that a lot of TCP
sockets are being opened.
Further testing showed that the number of threads being
opened, increases with direct relation to the frequency of
the remote calls being made by client (In any case, we
noticed that the number of threads exceeds 25, which to
our understanding is supposed to be the maximal amount of
threads in the thread pool).
 
Hi,
My apologies. It seems that we had a bug in our SW. The SW
programmer (Let's call him 'Y' for this matter), kept
registrating events within the thread pool.
Thank you for your attention.
 
Back
Top