Hi Jr,
can you try to reproduce the issue using Microsoft's RDCMan (Sysinternals)? I guess with MS RDP you actually mean mstsc.exe. If so, there are a couple of differences between mstsc.exe and the ActiveX control we are using. The same ActiveX control is also used by RDCMan, so it would be interesting if you see the same issue there.
Regards,
Stefan
Hi Jr,
in this case, I'm afraid you posted in the wrong forum/thread. This is all about the Windows client. I suggest you post your issue in the Royal TSX (for macOS) section or open a support ticket for further assistance.
Thanks,
Stefan
Hi Stefan,
I see, sorry. I'll try to recreate the issue in windows machine once I get one.
Regards,
Jr
Although this is an old thread I thought I'd response, because I have the same issue (and it seems to get worse with every version). I have quite a few connections in my document (1397 to be precise, created in 2012) and RoyalTS becomes really slow and sluggish after a couple of days of usage (I'm usually opening and closing quite a few RDP connections every day). The current state of Royal TS is (running in the background):
Hi Martin,
thanks for letting us know. We know that RDP requires a lot of RAM and since the RDP ActiveX instances are all hosted in the same process, it may come to congestions on the UI thread. Could you try to use the FreeRDP plugin? This is started as a seperate process. The rendering is still on the very same UI thread for all instances but I guess it may be more efficient since all the other stuff is handled in a deciated process.
Regards,
Stefan
Hi Stefan,
thanks, that was really helpful, there is a massive difference when it comes to memory consumption (now after one day with 5 open RDP sessions it's at 330 MB) and CPU usage is a lot less as well.
Only the UI still feels a bit sluggish when it comes to editing connections, but here I guess I need to do the work and delete old stuff ;-)
thanks again !
BR,
Martin
Glad to hear that helped. The connection properties UI is still based on an old UI framework called WinForms - which can be sluggish. We are currently working on a solution for that but this still takes some time...
Regards,
Stefan
I'm the OP. Glad to see there is finally a workaround to this issue!
I switched to the FreeRDP plugin and there is a world of difference. Connecting to the remote machine is much faster, much less RAM usage, and it seems interacting with the remote machine is also much quicker. However, I have run into an issue where the connection seems to be "frozen" and I can't interact with anything on the remote machine. It usually seems to happen on the initial connection - the icons/desktop will "flash" around for a few seconds (like normal) and then it freezes and I need to reconnect. I also use the FreeRDP plugin on Mac, but don't experience this.
I agree that the UI is still very laggy/slow. I use both RoyalTS and TSX - the UI on Mac is lightning fast and responsive. I look forward to the new UI whenever that may come.
Hi Riley,
I haven't seen the frozen RDP session issue myself yet, would be interesting to figure out what's going on here.
The implementation is quite different to the mac one though. While we implemented FreeRDP from scratch ourselves, on Windows we use the wfreerdp.exe and use a feature to render the session to a specified GDI target handle. Big advantage is that the process is isolated (similar to what we do on the mac), so when a session has a problem, it probably won't affect the whole application.
In any case, we are working on something similar we have on the mac with FreeRDP. It's still early days but we do plan to bring the same implementation to Windows.
I've had the same problem (4-5 RDP sessions open, and system becomes unresponsive).
I switched 2 of my sessions to FreeRDP and I think it's an improvement. Eventually will switch all sessions to FreeRDP and report back
riley.foster
Hi All,
Looking to see if anyone else has experienced similar issues. This has happened to me for quite some time - over a year, but I've been too lazy to report it.
Basically, it seems that after an extended period of time (several days) the RoyalTS app window becomes almost unusable. Moving the RoyalTS main window around the monitor or between monitors is very slow. I will click to drag the main window around and it takes 5-7 seconds before the screen follows. Also, moving between connections/tab in the interface is extremely slow. After clicking a tab it takes 3 - 4 seconds before the screen changes and the tab will accept input. I predominantly use RDP to 7-10 servers as a time and those connections might remain open for days.
Closing/reopening RoyalTS will resolve the issue.
Riley