Sorry, I got confused. You do not have two computers with the problem? Only one?

Yes, one computer with the problem

I am also experiencing this problem with 2.1.5 where it wasn't in 2.0.13.

I run Vista SP1 32bit w/o aero.

There have been times when minimizing a maximized RDTabs takes 5 seconds and other times where the app goes into lala land and the mouse will only move every 5 seconds or so and you have to navigate over to the minimize again and click.

It acts the same as a single threaded app trying to read/write data to a serial port that "locks" up the app while waiting for data.

Is it possible for you two to communicate to see what you have in common? dpreuss - do you have any other apps that experience this similar behavior? SP1 seems buggy to me in some instances (I am going to open a case with Microsoft next week because all my lab computers lose communication with random network servers after being online for 20 hours). The SP1 RDP control, in particular, hangs for a moment while connecting to the first connection. That one is due to about 1000 registry accesses happening on connect. Very inefficient! I've covered that in another post and in the changelog. I know yours is due to the control box. I cannot replicate this issue on my pre or post-SP1 Vista boxes, unfortunately. Any help you guys can give me by working together would be great.

BTW, check out this thread. Another user was having some performance problems and found a 3rd party app was causing the problem (IE Pro). I have no idea if it is related. Just throwing it out there. There are now three people reporting this locking-up-on-minimize problem and I'm clueless because try as I might, I can't replicate it. :-(

http://www.avianwaves.co...lt.aspx?g=posts&t=84 

Question: Do you run RD Tabs in "Full screen mode" or normal? How many tabs are open when this happens? How many other applications are open?

I know I had 1 session active potentially 2 at the time I wrote the previous response. I am at home now and am not experiencing any problems as previously mentioned. The only difference is that I am not docked and using a dual monitor. It may be related to that or the resolution 1920 x1200.

I ALWAYS run maximized, however the proiblem didn't seem to follow that as I could window RD tabs and clicking the maximize would excerpt the same behaviour.

Other than that I am at a loss for ideas

Yea those are two things I can't test. I don't have a monitor anywhere near that high of resolution (my max is 1280x1024) nor do I have a laptop that uses a docking station. Good thoughts, both. If anybody can reproduce consistantly, I might be able to figure something out.

Any other apps do this? Particularly, .Net apps, as I really seriously do not do anything special during the window resize/maximize/minimize events. Code hasn't changed there since 1.x! Can't for the life of me think of what changed between 2.0.x and 2.1.x...

I've been doing some testing here and found that it only shows up when I'm dual screen mode even if the second monitor (primary) is 1024 x 768. The second I pull the video cable and lose the second monitor everything works as expected.

That is very peculiar, but a very good find. Thank you for that. I'm running dual monitor without any problems, so that begs the question... What make/model of video card? What driver version?

Laptop or Desktop?

Laptop

Dell Latitude D820
Dual Core 2.0 GHz
2 Gig Memory
Intel 945GM - Latest driver on Intel's website

The video driver could very well could be a part of the cause. We use a lot of Dell where I work, but I don't think we use any that have Intel video. We usually opt for the mobile ATI or nVidia.

I know you tried the latest driver, but what about legacy drivers? For instance, the one that comes on the CD that comes with your laptop? It would be interesting to see how that works...

Also, are you using a docking station like the D-Port? If so, is there any change of behavior between docked and undocked?

It's not the Port replicator as I can remove the video cable from it in effect going to single monitor mode and not have the issue. I also have a coworker that uses the Dell driver and has the same issue.

I dual boot with XP and am not experiencing the same issues, everything works as expected. However this problem didn't show up until I updated from 2.0.

I've got a Laptop, HP nx7400 with Intel Graphics Engine, 945GM, same as dpreuss.
I experience the problem in full screen, sized, single monitor and dual monitor.

My laptop has a screen-res of 1280x960 and my monitor, which I use when I'm at work, no laptop-screen then, is 1920x1200.
I had the problem with dual-screen with two screens at 1280x1024, but I don't have this setup anymore.

Current driver-version of the graphics card: 6.14.10.4820

Are you able to click on the control box button before it hangs/pauses? (as opposed to hanging when you mouse-over) If so, I can email you a debug copy that will log timestamps between every step and we can see where the problem is occurring exactly. Use the contact form on this website to email me. Thx.

Hi Timothy,

Yes, I can click the button, and then it freezes/pauses/hangs.

I'll send you a msg through the contact-form.

I noticed today that if I use "Connection->Exit" RDTabs closes immediately (as expected). I have been able to reliably replicate this in between random "Minimize, X" actions.

Is there a difference between those 2 function calls?

That's the same thing that I had experienced. Same goes if you right-click on the icon in the taskbar to maximize, minimize and/or close the program...

Well, I'm just using .Net Framework event handlers. It's the same function as far as RD Tabs is concerned, but I don't know precisely what the framework is doing to wire up the event handler to the control box, as I don't have to write that code. If those alternate methods are working but the control box is not, I hate to say it, but it might be a framework/Windows/driver issue. Not to say something new I'm doing isn't aggrevating it (why 2.1 does it for you but 2.0 doesn't), but as far as the act of closing and throwing warnings up (are you sure) and all that, that's identical function calls.

When you Connection->Close, it's just calling Me.Close(), which fires the FormClosing and FormClosed events before terminating the application (application exits when the main form is closed). All I do in FormClosing is check "are you sure" and things like that. But that's it. There's no code in FormClosed. I don't even handle that event. The framework ties up all the final loose ends (saving settings and stuff). That's all boilerplate code that I can't even change (generated by the compiler).

I just read the debug output I got emailed from Iskander running the debug version of RD Tabs and I can tell that the event handlers are firing after the pause. The event handler code all executes within the same second. So something is delaying the action between the controlbox "mouse down/up" events and when RD Tabs receives the "FormClosing" or "Resize" events.

Are you guys running any other .Net Framework 2.0 applications? I am curious if anything else does the same thing... somewhere!

I'm running multiple .Net 2.0-applications, including ones I develop myself. I've got VS 2005 SP1 and VS 2008 installed, and have no problems with any other application and the controlbox or any other issue...

This might be stretching things, maybe, but could it be possible for me to receive a copy of the code and debug the issue? If needed, an NDA would be no problem...
If you don't want that, I'll completely understand.