Beta: sometimes the wrong session is opened
I'm not sure whether this problem is related to this beta or not, but me and my colleagues have frequently found that when doing a search in the search field and then immediately pressing "Enter" to open a RDP session results in that an RDP session to a different server is opened.
The reason why i don't think that this is related to the beta version is that at the same time that we installed the latest beta version we also added quite a lot of new session to RDM.
I was able to reproduce the problem, from what i saw was that when you are typing the name of the server, the tree is continuously updated with matching servernames.
When you then do a very quick "Enter" right after you finished typing in the name, you can see in the list pane that at the moment you press enter, the list did not quite finish displaying the final match to the name of the session.
What then happens, is that the first match of name of the session when about 4 out of 5 characters have been typed in is opened. The match of 4 characters is the wrong match.
What is comes down to essentially, is that the enter key is not queued to wait for the session list to finish displaying the end result of the search.
We use a mdb database on a share which currently has a size of about 1,5 mb.
All Comments (6)
Hi,
i created a bug report for this in this bugs-forum, because that makes it easier to track this problem, but also because i found out this this problem seems to not exist in the older version 5.8.2.0.
I did another test and i noticed that this is what actually happens when you press enter too quickly:
The last session that you had opened is opened again. So the problem is not that it opens just anything it has found during typing.
How to reproduce:
1. We are using a mdb database that is present on a share, maybe it would be a good idea idea to try to reproduce the problem by using an mdb file as well.
2. Make sure there are about 10 groups, each with about 60 RDP sessions in it. Some with sub-sessions that represent a browser session.
3. Expand one of the groups.
4. Select one of the first sessions in the list.
5. Do a search for a session that is present almost at the end of the list. Do the search by typing in the last 5 characters of the name of the session. Type it in quickly and immediately after typing it in press the "enter" key.
6. The previously selected session will now be opened, not the one that was matched by the search.
I reinstalled the older version 5.8.2.0 and was unable to reproduce the problem in that version. I am under the impression the older version was much faster at displaying the results when searching.
I think this problem has been introduced in the beta (tested on 5.9.0.19-5.9.0.21) and should therefore be solved before the final version is released.
edited by ruudboek on 2/14/2011
edited by ruudboek on 2/14/2011
Hi,
I will release the version 5.9.0.22 tonight, can you verify that it's fixed.
David Hervieux
It seems to be fixed which is great, the downside however is that it is a lot slower in finishing the search before the opening of the session is started.
It is a great deal slower actually, it takes about 4 seconds after i press enter before the session is being opened. That used to be just about instantly.
I personally don't think that 4 seconds is acceptable.
Are there perhaps some optimizations that can be made to speed it up?
Hi,
This is not a performance problem, I will verify if I can wait a shorter time for each pressed key.
David Hervieux
Doh, sorry it's my fault, I slowed down for my test... I build a new version...
http://remotedesktopmanager.com/download/Setup.RemoteDesktopManager.5.9.0.23.exe
http://remotedesktopmanager.com/download/Devolutions.RemoteDesktopManager.Bin.5.9.0.23.zip
David Hervieux
I've tested it, it's perfect, the speed is great and i have not been able to reproduce the problem, so this looks like it is solved. :)
Thanks david, especially for for the quick response.