2023.3.20 - RDM Crash when RDP session Screensize is "Work size area"

Hello,

we reproduced your issue and a ticket has been sent to the Engineering Team.

Best Regards,

Hi

Sounds good!

I can confirm that it is also present in .22 if you haven't tested yourself :)

Regards

Just curios, is this fix expected in next release .23+ ?

And are you gunning for a release of .23+ before the weekend starts?

Regards Lars

Unfortunately, this hasn't been fixed in .24 either :(

Hello,

we are still investigating the crash, there's no ETA yet on the fix.

Best Regards,

Hello

I've been able to reproduce the issue somewhat intermittently; given the symptoms that makes sense as it appears to be timing related.

Does the problem occur for you consistently, or only sometimes?

I'd like to ask a little more information:

• In the "Display" tab, what do you have configured for "Screen sizing mode"?

• In Options > Types > Sessions > Remote Desktop (RDP), in the "Advanced" section; is "Force reconnect when monitor is changed while using "work area" display mode" checked?

Thanks and kind regards,

Hello

Thanks for the information. As a follow up question; last week I managed to reproduce once or twice connecting to a Windows Server 2k16 system. Today I've been trying with a Windows Server 2k22 server but haven't seen the issue once.

What server version(s) of Windows are you connecting to?

Thanks and kind regards,

Yes, it seams that only Windows 11 and Server 2022 seams to have the issue.

and I mainly connect to 2022 :D

Just a random thought, could it be something with newer RDP uses both TCP and UDP? or is that part entirely mstsc.exe?

Hello

I do believe I found the issue here: it's very timing dependent so by that nature, some users would see this problem every time, some would see it intermittently and most would never see it all. I was only able to reliably recreate the issue by running a concurrent fuzzing tool to randomize thread scheduling.

I'm afraid the fix did not make it in time for today's 2023.3.25 release but should be in the next update. After you upgrade to the next version, please do post back if you still experience issues. I will try to update this post once the next version is available.

I apologize for the inconvenience.

Kind regards,

Hi

I'm just happy there hopefully will be a fixeven if that means waiting a few more days.

I will for sure report back when I have tested .25

Regards Lars

Think I might have misunderstood you, but I have just upgraded to .25, and as you said, the issue still persists.

But I will report back again when next release is out :)

Hello

Yes, apologies for any confusion - my fix didn't make it in time for the .25 release but will be in the next version.

Thanks for your patience.

Kind regards,