Memory exhaustion on Win10 Pro via RDP

Hello,

I'm using freerdp to check RDP availability of a Win10 virtual machine running under Proxmox 5.2 (kvm). The command used is:

/usr/bin/xfreerdp /cert-ignore /auth-only /u:$USER /p:$PASS /v:$HOST

Every time this command is launched, the svchost.exe process related to "TermService" grows around 8MB in its "private bytes" memory. That amount is reduced to around 5MB if you set the display size in freerdp to 1x1 (/size:1x1). That memory is never returned to the system and in a few days some messages related to "resource exhaustion" are logged and eventually RDP stops working. At that time, that svchost.exe process has more than 10GB of "private bytes" (VM has 20GB total memory). Win10 needs to be restarted for RDP to work again, as restarting TermServices service does not help.

Adding memory or a bigger pagefile to the VM only delays the time when RDP stops working, it will eventually fail anyway.

I dont know if this is caused by FreeRDP shutting down the connection without notifying the RDP Server properly or if it is a Windows issue or a configuration issue. It's very easy to create a DoS to a Win10 Pro RDP
server if you have valid credentials. I haven't tested any other Windows version nor any other virtualization environment. Luckly, it doesn't happend if you dont have valid credentials.

Please, give it a look to find out what could be causing this behaviour.
Thanks a lot