Mac Remote Desktop Crashing When Copying

Mac Remote Desktop Crashing When Copying
2

Upvotes

Upvote

 Oct 06 2021
6 Comments (6 New)
New

Hopefully this is the correct place to post this now that the UserVoice website has been shut down.

 

The latest versions of Remote Desktop for Mac have introduced a regular freezing problem when copying anything within a workspace. This is particularly bad in the Remote Desktop Beta, which we've currently abandoned, having used this for the last few years, and occurs quite regularly in the App Store version.

 

Force quitting and then relaunching does at least retain the workspace, but until the force quit there is no interaction, just the blue spinning circle.

 

This is on a 16Gb M1 MacBook Pro connecting to a Windows 2019 RemoteApp server.

Comments
Senior Member

This problem has continued over to a new M1 Pro 14" MacBook Pro running Monterey v12.0.1. Remote Desktop is unusable and for now we've abandoned it.

Senior Member

This problem has now started happening on a colleague's new M1 Pro 16" MacBook Pro running Monterey v12.0.1 that has been set up without any application or preference file transfer, i.e. from scratch without any influence from an existing Mac. MRD v10.7.1 and MRD Beta 10.7.2 are used.

 

All of the above Macs connect to workspaces on Windows Servers 2012, 2016 and 2019 RemoteApp servers, mostly using FileMaker Pro v19.

Senior Member

We have moved away from Remote Desktop for Mac while this problem exists and have been using Jump Desktop to connect to the same workspace apps from the same servers and have had none of these problems. Jump Desktop is also Apple Silicon native.

 

In addition, Jump Desktop supports proper international keyboard mappings. We'd like to return to Remote Desktop to mirror what many of our clients are using, but cannot currently develop in it due to the frequent crashing.

Senior Member

Still testing the latest beta (10.7.2) releases and the interesting behaviour is that once MRD Beta freezes, it also prevents access to the destination Mac app for a number of minutes, which does eventually respond.

 

However, upon regaining access to the app and testing whether the original text could be pasted, it then became unresponsive again for a while, then OK again after that. This could be repeated until MRD Beta was forcibly quit.

 

Back to Jump Desktop again for now for reliability and proper international keyboard mapping. However, it isn't free and doesn't provide a proper SDI experience, behaving more like the old MDI.

Senior Member

We are still experiencing this problem after upgrading to v10.7.3 (1966). No Mac app was involved, just an internal copy of some text within FileMaker Pro v19.4.1 and Remote Desktop stopped responding.

 

Again to emphasise, this doesn't happen using the same workspaces within Jump Desktop, Windows RemoteApp connections or using FileMaker locally.

Senior Member

I believe we've finally found the problem with the regular crashing when copying.

 

We also run Parallels on our Macs and the Parallels Toolbox is installed, which includes a Clipboard History utility. Retrospectively, it may seem obvious that a clipboard utility could cause Remote Desktop for Mac to become unusable, but we've a number of MacBook Pros here that have had varying symptoms, which has muddied the water.

 

We'll post this on the Parallels forum as well, but at least we have finally resolved the problem.

 

The lack of any feedback from Microsoft has been very disappointing.