Memory leak in Remote Desktop version 1.2.5559.0 (x64) and a few versions back

Memory leak in Remote Desktop version 1.2.5559.0 (x64) and a few versions back
1

Upvotes

Upvote

 Aug 05 2024
5 Comments (5 New)
New

Microsoft Remote Desktop has a memory leak. This started a few versions back; I thought maybe it would be fixed in succeeding versions, but it has not. You can watch with Task Manager and see it slowly consume more memory. It starts out with about a 50MB footprint, but I've seen it at over 4GB before I had to kill it. Right-clicking on the icon in the system tray did nothing (unresponsive). So there is an issue somewhere. I'm not sure what triggers the increase in memory utilization, as it seems to be stable at first.

 

Edition Windows 10 Pro Version 22H2

OS build 19045.4717

Experience Windows Feature Experience Pack 1000.19060.1000.0

Comments
Copper Contributor

Confirmed.

 

My original problem was that the client did not reconnect, then I opened the task manager and saw that there are multiple Remote desktop subprocesses running. I killed them then I could re-connect.

Another problem is that sometimes the connection freeze for a couple of seconds if I put the session to the tray.

 

After all, is started to looking for a newer version but seems we are in latest. Then I found this post for this given version 1.2.5559.0 (x64) and checked this memory leak problem. I can see that the memory consumption creeps slowly up.

 

We run this client in:

OS Name: Microsoft Windows 11 Business
OS Version: 10.0.22631 N/A Build 22631
OS Manufacturer: Microsoft Corporation

Copper Contributor

Ok, I think I may have determined the genesis of this issue.  If the remote connection drops, Remote Desktop seems to start eating memory:

RemoteDesktopMemoryLeak1.png

Here you can see it had consumed over 7 GB of memory!  The remote connection had dropped (evidently because the remote server was rebooted).

 

After closing the desktop app, the main process still remained, so I had to manually kill it via Task Manager:

RemoteDesktopMemoryLeak2.png

 

Copper Contributor

Well, the above is not entirely true.  Remote Desktop seems to be consuming memory even when the remote connection is viable.  I locked the remote session overnight, and the next day Remote Desktop had consumed over 5GB:

SQLEngineer_0-1724445833025.png

But then, when I closed the remote session window, it suddenly jumped to over 6GB before stabilizing at 5.1GB and then dropping again to 4.5GB.  All this without a remote connection.  Not sure what this app is doing, but it seems to be a sick puppy.

Microsoft Remote Desktop

Version 1.2.5560.0 (x64)

 

Copper Contributor

It's interesting that no one else is bothered by this issue.

 

Now I started to replace the MS Store Remote Desktop App version to the other which is installed by MSI installer since there is a newer version: RemoteDesktop_1.2.5620.0_x64 and this article prefers it over the store app version. https://learn.microsoft.com/en-us/azure/virtual-desktop/users/connect-windows?pivots=remote-desktop-...

BTW, why? What is the difference between the clients deployed from the store or via MSI installer?

Another question is how to maintain the lifecycle of this client app in all workstations across the company?  Why can't MS distribute the this client as part of the OS and update it once required? What is the concept behind?

 

Thank you in advance if anyone can shed light on above questions.

 

 

Copper Contributor

After noticing Remote Desktop was again consuming memory, I closed my remote session and closed the Remote Desktop app.  Then I tried to close the background app via the System Tray, by right-clicking (and left-clicking) on the Remote Desktop icon, but it was unresponsive; no context menu appeared:

SQLEngineer_0-1724948956599.png

 

At this point it was consuming over 5GB of memory, without any remote sessions.  I had to kill it via Task Manager.

 

This app has issues, Microsoft!