TS Client ramping CPU and leaking memory badly

  • Thread starter Thread starter Dan Forest
  • Start date Start date
D

Dan Forest

Guest
I recently started having a problem with mstsc.exe taking the CPU up to
60-70% and leaking steadily (watched it go to 500 MB+ before stopping). This
is with a single remote desktop session active. Initially all looks OK, but
after some time the leak begins and doesn't stop. Closing the remote session
does not kill the app or release any memory. I recently installed some MS
security updates and that seems to coincide with the problem, however I
haven't been able to find anything on the web linking the updates to this
problem. The updates applied were:

KB945553
KB941693
KB948590
KB948881

In addition, I tried uprading to terminal services client v6, but that did
not help. Is anyone aware of this problem and a possible fix? Thanks.

Dan
 
Re: TS Client ramping CPU and leaking memory badly

Check following link, see if it works for you
http://support.microsoft.com/kb/907572

Ratnesh

"Dan Forest" <DanForest@discussions.microsoft.com> wrote in message
news:F89A218D-EDFD-4EFD-BCE4-74F39494B2D9@microsoft.com...
>I recently started having a problem with mstsc.exe taking the CPU up to
> 60-70% and leaking steadily (watched it go to 500 MB+ before stopping).
> This
> is with a single remote desktop session active. Initially all looks OK,
> but
> after some time the leak begins and doesn't stop. Closing the remote
> session
> does not kill the app or release any memory. I recently installed some MS
> security updates and that seems to coincide with the problem, however I
> haven't been able to find anything on the web linking the updates to this
> problem. The updates applied were:
>
> KB945553
> KB941693
> KB948590
> KB948881
>
> In addition, I tried uprading to terminal services client v6, but that did
> not help. Is anyone aware of this problem and a possible fix? Thanks.
>
> Dan
 
Re: TS Client ramping CPU and leaking memory badly

Thanks for the link. I don't think I was ever connecting to the serial port
on the remote computer, but can't be 100% certain. I solved the problem by
upgrading to v6 of the terminal services client. If I was connecting to the
serial port, the upgrade may have cleared out my existing settings, thus
'fixing' the problem. Thanks.

Dan

"Ratnesh Yadav [MSFT]" wrote:

> Check following link, see if it works for you
> http://support.microsoft.com/kb/907572
>
> Ratnesh
>
> "Dan Forest" <DanForest@discussions.microsoft.com> wrote in message
> news:F89A218D-EDFD-4EFD-BCE4-74F39494B2D9@microsoft.com...
> >I recently started having a problem with mstsc.exe taking the CPU up to
> > 60-70% and leaking steadily (watched it go to 500 MB+ before stopping).
> > This
> > is with a single remote desktop session active. Initially all looks OK,
> > but
> > after some time the leak begins and doesn't stop. Closing the remote
> > session
> > does not kill the app or release any memory. I recently installed some MS
> > security updates and that seems to coincide with the problem, however I
> > haven't been able to find anything on the web linking the updates to this
> > problem. The updates applied were:
> >
> > KB945553
> > KB941693
> > KB948590
> > KB948881
> >
> > In addition, I tried uprading to terminal services client v6, but that did
> > not help. Is anyone aware of this problem and a possible fix? Thanks.
> >
> > Dan
>
 
Back
Top