Frequent crashes on High Sierra

Frequent crashes on High Sierra

avatar

After upgrading to macOS High Sierra, I am now experiencing frequent crashes of RDM 4.5.1.0.

Can you please instruct me on how to get you the bug report/crash dumps so you can investigate? Unless, of course you have already found this yourselves... :-)

/Jesper

All Comments (39)

avatar

Hi Jesper,

Could you try this version: https://www.dropbox.com/s/4xntz0685wf2p52/Devolutions.RemoteDesktopManager.Mac.4.5.1.1506450745.dmg?dl=0 and tell me if this appears to resolve your issues?

Best regards,

Xavier Fortin

avatar

I will let you know the results later today whether or not it fixes it.

avatar

It seems to have resolved it on High Sierra. I will continue to try and get you some video on RDP Engine V5 performance tomorrow.

avatar

Sorry, Xavier, it just happened - the good news is that I could run a LOT longer (4-5 hours) before it did... :-)

avatar

It makes sense. Other users also still get them but more scarcely. Were you doing anything particular when it crashed? Were you creating/editing a session? Or opening one?

Best regards,

Xavier Fortin

avatar

Trying to open a session. It seems that it has a fixed number of sessions before it crashes. I've been thinking about counting them, but my guess is that somewhere from 15-20 opening sessions will crash it. Perhaps a memory leak somewhere?

avatar

Most likely related to unwarranted access attempt on disposed object. The previous crashes, that happened more often, were caused by observers being kept on released object. My guess is that something similar is happening. It's probably not about the observer though (I'm pretty sure I've been pretty thorough on this one).

I'll keep your observation in mind while looking into this.

Best regards,

Xavier Fortin

avatar

Just happened 3 times within the last 2 hours, and I'm on 4.5.2, so I'm not sure you have it all fixed... :-)

avatar

Yeah, don't worry, I'm on it. I've been able to reproduce some of them. I've not tracked them down yet though.

I'll keep you inform on any progress.

Best regards,

Xavier Fortin

avatar

Hi Jesper,

I've just finished building a version that, I think, addresses the crashes with opened sessions. I'd like you to test it and tell me if you get any other crashes.

Here is the version: https://www.dropbox.com/s/6j639g46f2npxvd/Devolutions.RemoteDesktopManager.Mac.4.5.2.1507045693.dmg?dl=0

Best regards,

Xavier Fortin

avatar

Still happens. I also found an interesting way to make it happen:

1. Open 2 or more sessions (in my case both were Windows Server 2012 R2)
2. Right-click and Force Quit RDM
3. Open RDM again. When it asks "Do You Want to Restore the Last Opened Connections?", click Open, and it will pretty much crash instantly!

/Jesper

avatar

This is weird. I can't seem to reproduce this one. I doubt this is relevant, but what Data Source are you using?

Could you also run RDM via the Terminal, reproduce the crash and send me the terminal output?

Here's the command if RDM is in the Applications folder: "/Applications/Remote Desktop Manager.app/Contents/MacOS/RemoteDesktopManager"

Best regards,

Xavier Fortin

avatar

I'm using a File based data source. Here is the Terminal output:

2017-10-03 14:05:56.807 RemoteDesktopManager[56997:12657242] Failed to connect (butBoldClick) outlet from (ConnectionHandbookViewController) to (NSButton): missing setter or instance variable
Stacktrace:


at <unknown> <0xffffffff>
at (wrapper managed-to-native) Tie.Rdp.NativeRDP.CheckEventHandles (intptr,intptr) <0x00012>
at Devolutions.RemoteConnections.RDPSession.UpdateProcess () [0x0004d] in <5c5f358bea3146bd9b434df91296fb4a>:0
at System.Threading.ThreadHelper.ThreadStart_Context (object) [0x00022] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x0008f] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) [0x00004] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object) [0x00035] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at System.Threading.ThreadHelper.ThreadStart () [0x00017] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0
at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) [0x0004f] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0


Native stacktrace:




=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================


Abort trap: 6

avatar

Well, it looks like we've found another issue with the Engine V5. RDPSession.UpdateProcess () is only used with RDP sessions using the Engine V5.

This is weird though, since I'm pretty sure I was testing with at least 2 RDP sessions with V5. I'll check this out.

Thank you for the output.

Best regards,

Xavier Fortin

avatar

Hi Jesper,

I've reproduced the issue. Is it possible that at least one of the session you were opening had the Sandboxing off?

This piece of code should only be called in this case.

We're looking into this right now.

Best regards,

Xavier Fortin

avatar

Anytime, just let me know, as long as I can help. Looking forward to the fix.

avatar

Interestingly, Sandboxing WAS set to False. I guess it must have crashed at some point after I set it back to True. When RDM crashes, it doesn't save the settings, you see...

I will be happy to test after you get a new build out, but for now, I'll turn sandboxing on again... ;-)

avatar

Looks like 4.5.3.0 is out to fix this. Thank you!

avatar

I still have the problem on High Sierra that the program crashes. The latest version does on my system not solve the problem.

Wat more can be done?

avatar

Hi,

This is weird. Are you on the latest High Sierra version?

Did you notice any pattern to the crashes? What are you doing when the crashes occurs? Which type of sessions, if any, are opened when it crashes?

Could you run the the app via the Terminal.app (like so: open "/Applications/Remote Desktop Manager.app/Contents/MacOS/RemoteDesktopManager"), reproduce the crash and send me the terminal output via private message?

Best regards,

Xavier Fortin

avatar

I have the same issues for months... Its horrible!

After a while the program crashes if more then 2 RDP session active!

avatar

I'm on 10.13.1.

I cannot even open 1 session.
When i do so, RDM quits.















avatar

I think, it has to do with tabbed sessions. Tabbed and Undocked quit the app.

avatar







This look like an issue that as been fixed internally. I'm not able to reproduce it anymore though, even without the patch. What RDP engine are you using with your RDP sessions (V4 or V5)? Do you have OpenGL enabled? Do you have Sandboxing activated?

You can find the option for the engine under the General tab of your session and the OpenGL and Sandboxing options under the Advanced tab. If these values where left to Default, the app Preferences values are used (under Session Type -> RDP).





With any sessions or only RDP sessions? Could you also try switching the RDP engine?

Best regards,

Xavier Fortin

avatar

Hi,

The issue where RDM crashes after a while of having multiple RDP sessions opened simultaneously should be resolved in the version 4.6.1.0 of RDM. The version probably hasn't been pushed to you yet. You can download it manually here: https://cdn.devolutions.net/download/Mac/Devolutions.RemoteDesktopManager.Mac.4.6.1.0.dmg

Best regards,

Xavier Fortin

avatar

Merci bien, Xavier! Just curious, would the issue with V5 performance also be fixed?

/Jesper

avatar

Hi Jesper,

In our tests, performances with multiple RDPs (V5) were much better. We'd appreciate if you could tell us if this appears to improve performances for your.

The performance issues and the crash on multiple RDP sessions seemed to have been caused by the same root problem. We've fixed that and it should be a lot better now.

Best regards,

Xavier Fortin

avatar

Now I'm getting 2 (two) "Disconnected" dialog boxes when trying to connect to certain servers with V5, sometimes it says "Can't connect to host !". What can I do to diagnose that?

Also, it seems to be isolated to Windows Server 2012/2012 R2/2016 R2 connections. 2008 seems to be working fine.

/Jesper

avatar

Hi Jesper,

This is weird. I can't reproduce on any of our server. Can you send me you Application Log and generate the RDP log on one of the faulty sessions?

Best regards,

Xavier Fortin

avatar

Xavier, I just sent you the log file. The weird thing is that this seems to be related to the black screens under RDP V4: https://forum.devolutions.net/topic28417-black-screen-upon-connect.aspx?lastpage=1#post108847

Could it also be something to do with Sandboxing?

avatar

Maybe. Have you tried without it?

I'd still like to find what's causing you such trouble and fix it though. I'll start looking into your log.

Best regards,

Xavier Fortin

avatar

Sandboxing didn't make a difference. I turned it off, but it happened anyway.

avatar

Hi Jesper,

I forgot to ask but, has this started in the version 4.6.1.0?

Best regards,

Xavier Fortin

avatar

Hi Jesper,

Are the affected sessions on Microsoft Azure VMs, Hyper-V VMs or on Load Balanced environment (using a Connection Broker)?

Best regards,

Xavier Fortin

avatar

With V5, the 2x "Disconnected" boxes started in 4.6.1.0, but the black screen upon connecting (now gray in 4.6.1.0 using V5), i.e. difficulty creating a connection the first time is not new, that dates back a long time: https://forum.devolutions.net/topic28417-black-screen-upon-connect.aspx

I've also had conversations with Benoit about it in the past.

avatar

The VMs are running on our own Hyper-V server, and it seems to be worse when connecting while inside the office than through the VPN connection.

We upgraded the hosts to Windows Server 2016, and same with the Guest OSes, but to no avail.

It has happened with other connections, too, but less frequently. So I would guess that it may be a network/handshake issue in the FreeRDP implementation?

avatar

Hi Jesper,

Without being able to reproduce, we're really only scratching our head to no avails. Would that be possible to give us some kind of restricted access to one of the faulty server (ideally one of no importance) so we can attempt to reproduce on our side and hopefully come with a fix (this could also apply to the black screen issue)?

I know this is less than ideal, but we're pretty much walking in the dark.

Best regards,

Xavier Fortin

avatar

That I can do. Let me get with the network admin and get you setup. You will need a Barracuda VPN client, but I can send to you as well.

avatar

Glad to hear it!

Best regards,

Xavier Fortin