Too Many Tabs = Protocol Error?

Hi,
This is a know issue and we are still trying to find a solution. The problem is that Windows8 and Windows 2012 take about 150/200MB per connection. For now RDM is a 32 bit application and this is why we get the limitation. RDCMan has the same exact issue.

This is very annoying and we are aware of that.

Hi David,

Thanks for the reply. I understand, hopefully a fix can be worked out! A x64 version would be great but I imagine that is a lot of work.

Thanks,
Paul

The problem with a x64 is that we have so many technology integrated, it's complex. However this is on the roadmap for sure.

for the time being you can try trick the application to use more memory, running this neat tool against the executable http://www.techpowerup.com/forums/showthread.php?t=112556. It worked for me on me on windows 8, right now I'm able to actually open more than 4 tabs at a time with RDM using around 1242MB of RAM with 11 tabs opened.

Hi,
Thank you very much for the tip. We are currently working on a x64 version of RDM. We expect a beta in the middle of March.

Hi,
I have integrated this change in the build system. The next beta will be Large Address Aware.

Thank you again

Great news David! It's incredible it allocates so much memory at the start of the session and later it runs just with 350mb or so with all sessions opened.

The large address aware program has worked for me as well. I haven't experienced a crash yet today and I have 9 tabs open right now. RDM is using about 1,400 MB of RAM without trouble.

For those of you who need to take advantage of that capability you must adjust your OS. Please read
http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm

Hi,
The new beta is released.

I've installed the new beta and it seems to run fine, I've managed to reach 500+ MB memory usage whereas previously no more new connections were possible at 400MB (which doesn't seem much).
That's with Windows 8 Pro x64.
Wouldn't it be possible otherwise to launch rdp connections as separate processes ? It might also improve the stability of the program...

Hi,
We are currently working on the 64bit version of RDM. For this version we have to create a launcher for some connection type that are incompatible with 64. This is the first step for a multi-process launcher even in 32 bit.

Ok, that's good to know, keep up the good work :)

can you provide a status if this protocol error issue has been resolved in a newer version?

I don't think that Microsoft is gone a fix anything. We can only find workaround like the 64bit version or integrate FreeRDP as a replacement
edited by dhervieux on 4/2/2013

I didn't mean microsoft. Has this been fixed in RDM? Your reply wasn't really an answer.
If a workaround is a 64bit version, then is the 64bit version complete?

Ok,
Sorry for the misunderstanding. The 64bit version will be available this summer but we have updated the version 8.1 to be Large Memory Aware

http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm

any update on the 64bit version?

This is already implemented and it will be included in the next beta