Hi!
I suggest you open a support ticket here: https://www.royalapps.com/go/support-ticket-new
Not sure how big the dump file is but maybe we can find a way to transfer the file somehow privately.
Thanks,
Stefan
Hi!
A small update from my investigation:
1. it's extremely hard for me to reproduce the issue. At one time, it took almost an hour of constantly reconnecting to get a "hang/freeze". I assume the more CPU cores a system has, the more "unlikely" the hang will happen.
2. From what I can tell, the issue seems to be that the FreeRDP window is created on a non-main thread and then, at a later point in time, the same window is shown on a completely different non-main thread. While this may work in most cases, it can be a potential source for the hang.
3. To prevent that and rule this out as a root cause, the window creation and showing of the window should happen on the same thread, ideally on the main thread. The current wfreerdp.exe does not have any facilities to process cross-threading messages. Maybe there are other ways to accomplish that. To implement something like that, one of the freerdp team may probably need to take a look at it.
I'll keep you posted. Sorry for not having any better news at this time.
Regards,
Stefan
One of the FreeRDP maintainers was very kind and helpful and pushed a change which should fix the cross threading issue. I've just created a new Royal TS V7 Beta Build which also includes the new wfreerdp.exe with the fix:
x64 MSI: https://download.royalapps.com/RoyalTS/RoyalTSInstaller_7.00.20219.0_x64.msi
x64 ZIP: https://download.royalapps.com/RoyalTS/RoyalTS_7.00.20219.0_x64.zip
ARM64 MSI: https://download.royalapps.com/RoyalTS/RoyalTSInstaller_7.00.20219.0_ARM64.msi
ARM64 ZIP: https://download.royalapps.com/RoyalTS/RoyalTS_7.00.20219.0_ARM64.zip
Please note that this build hasn't been fully tested yet but I wanted to let you try this build as soon as possible to see if the wfreerdp.exe fix is effective. \
Looking forward to your feedback. Thanks!
Can confirm - it works a lot better now. Will keep monitoring and let you know if there are any issues.
Hi Alexander,
thanks for testing. Btw, we released an official beta release yesterday:
https://www.royalapps.com/go/kb-ts-win-downloadbeta
You might want to upgrade to this one.
Also, just out of curiosity: did you have a single hang since the update?
Regards,
Stefan
Thanks for the update! Yes, when I first launched it I had a couple of hiccups, but they went away. I will keep testing and let you know.
I still have people in my organisation reporting freezes of Royal TS when using its FreeRDP client. I will get them to create dumps if that helps.
Hi,
I am a new colleague of Birger who took over this topic.
We are using versioni : 7.2.50703 and I faced freezes recently.
I was able to do two dumps: one for wfreerdp and the other one for RoyalTS.exe
These dumps are quite big, even compressed about 400 MB.
Can I upload them somewhere?
Do I need to create a ticket or can you open one for me?
Hi David,
I'm happy to look at the dump files to see if there's something we can do. Please open a support ticket to discuss how to provide the dump files to our support team.
I guess the issue is not reproducable, right?
OK I will open a ticket.
And of course not reproducable.
I can work with Royal TS for 2 weeks with at least 3+ connections open, even lock my laptop and nothing happens.
Then suddenly on a busy day with only 1 connection and little time it''s freezing again...
Thanks for the additional details. I was assuming the freeze is happening more frequently. I've seen these freezes myself a couple of times. Roughly every 3 to 4 weeks for me and I couldn't figure out what was causing this. Since wfreerdp.exe is an external process it's hard to pinpoint and debug the issue. The memory dumps I did myself were not helpful but I will look at yours and see if I can find something actionable.
Daniel Breisacher
Hi there,
I'am using the Beta of RoyalTS V7. Sometimes when I try to connect on a server with freeRDP the complete application freezes and I have to force terminate it. The only thing you can see is a small bar in the left downer site of the window. For me it looks like a bug.
regards
Daniel
P.s. I configured the connection to use a SOCKS5 proxy.