Keep tab page open not working + slow opening connections
Hi,
.NET Runtime: 4.0.30319, .NET Version 4.6 or later
RDM Version 12.0.8.0 64-bit
Having recently reinstalled my OS and put the latest RDM on, I'm finding that when I close remote sessions (SSH, RDP, etc), it's not closing the tabs like it's meant to, and used to.
It closes the session, leaves me with a black screen, and stays open.
I've checked the properties of a connection -> User Interface -> Keep tab page opened on disconnect ... using either default or false.
I've checked the application level Options -> Advanced -> Auto close embedded tab on disconnect, as well as Types -> Keep tab page opened on disconnect
Additionally, connections seem to take a few seconds to load (giving me a loading ... progress bar), whereas normally in something like Putty or RDC Man, they'd be pretty much instant. Assuming it's slow pulling in from a database or such like?
Any suggestions anywhere?
All Comments (5)
Hello,
What type of data source are you using? In the case of a slow database, you would experience a lot of lag when opening RDM and when editing/saving.
Some of our users have hangs when closing RDP sessions (RDM Hangs when logging off RDP sessions), but not really for SSH.
For the slownesss to load the connections, you mention putty or RDC Man, meaning both SSH and RDP again. If both are affected, it could be DNS. They really dont share anything in common as far as RDM is concerned.
Best regards,
Maurice
Hello again
For the keep tab page open, we will try to reproduce.
Maurice
Thanks for the quick response.
What type of data source are you using?
Data source is just a default local one, Connections.db - and certainly not huge. I've got maybe 100 - 150 entries in there.
Some of our users have hangs when closing RDP sessions (RDM Hangs when logging off RDP sessions), but not really for SSH.
I've seen those threads, and suspect I'm experiencing those too, however, we've also got MBAM (malwarebytes) causing havoc as well, so hard to define at the moment.
I've just removed MBAM on my own machine, so I should get some clearer visibility if RDM is still hanging.
My issue isn't slowness on closing connections, but opening the initial connections.
Not sure what's happening behind the scenes, but it can take up to 4 seconds or so to establish the session and give me my remote console (be it SSH, RDP, whatever).
OS level DNS lookups are near instant, and establishing a RDP or SSH connection to them using other software is near instant, so I strongly doubt it's network conditions like DNS.
Even opening a connection, closing it, then re-opening it again can take a long time for that 2nd open.
Other users of the software, to the same hosts, don't have the same problem.
The 4 secs is when i get the loading bar.. 
Hunch would say it's taking a while to extra the info from the local data source and start making the connection. Can't see why though!
Hardware specs of my workstation: Xeon 3.5Ghz 4 cores, 16GB RAM, Win 10 Creators update.
At time of writing, 7% CPU utilisation, 54% memory utilisation., 0% disk utilisation , network traffic < 300 Kbps - so it's not overstretched local hardware!
Hello,
Are you all sharing the same data source or you all have your own local data source?
Do you encounter the same issue using RDM 32bit?
Best regards,
Jeff Dagenais
Hiya,
We all have our own local data source.
Thanks for the suggestion, hadn't really thought about that as a test.
It all suddenly behaves perfectly when running the 32 bit app.
Will switch to that as a resolution.
Thank you
