Odd V12 TCMD issue

[Jim Cook]

TCC 12.00.30 Windows 7 [Version 6.1.7600]
TCC Build 30 Windows 7 Build 7600

This does not appear to be 100% reproducible. I am using UltraStudio
10.10.0.1012 and twice now, I tried to launch an external tool (once a VDIFF
and the other was a VCS checkout) and UltraStudio appeared hung. Each time,
I restored a previously minimized V12 TCMD and the title bar included "Not
Responding". When I killed the TCMD, UltraStudio immediately proceeded.

--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.

 

[rconn]

TCC 12.00.30 Windows 7 [Version 6.1.7600]
TCC Build 30 Windows 7 Build 7600

This does not appear to be 100% reproducible. I am using UltraStudio
10.10.0.1012 and twice now, I tried to launch an external tool (once a VDIFF and the other was a VCS checkout) and UltraStudio appeared hung. Each time, I restored a previously minimized V12 TCMD and the title bar included "Not Responding". When I killed the TCMD, UltraStudio immediately proceeded.

I don't see any way for those to be related, unless UltraStudio is invoking TCMD to launch the external tool.

 

[Jim Cook]

I have now seen TCMD stop responding when it was sitting with a single TCC
tab in it and minimized. I was unable to restore it and had to kill it.

When this happens, it also appears that some other process gets sick until
the TCMD goes away. Before, I reported UltraEdit. This time it was a
different TCMD/TCC (V11) tab that stalled until I killed the V12 TCMD.

I started V12 TCMD, which created two V11 TCC tabs. I started a V12 TCC tab
and exited out of the V11 tabs, leaving a single V12 TCC in V12 TCMD. No
other V12 anything were being used. I minimized that and several hours later
went back but couldn't restore TCMD from the task bar back to normal.


On Mon, Oct 25, 2010 at 16:36, rconn <> wrote:

> ---Quote (Originally by Jim Cook)---
> TCC 12.00.30 Windows 7 [Version 6.1.7600]
> TCC Build 30 Windows 7 Build 7600
>
> This does not appear to be 100% reproducible. I am using UltraStudio
> 10.10.0.1012 and twice now, I tried to launch an external tool (once a
> VDIFF and the other was a VCS checkout) and UltraStudio appeared hung. Each
> time, I restored a previously minimized V12 TCMD and the title bar included
> "Not Responding". When I killed the TCMD, UltraStudio immediately proceeded.
> ---End Quote---
>
> I don't see any way for those to be related, unless UltraStudio is invoking
> TCMD to launch the external tool.
>
>
>
>
>

--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.

 

[rconn]

I have now seen TCMD stop responding when it was sitting with a single TCC tab in it and minimized. I was unable to restore it and had to kill it.

When this happens, it also appears that some other process gets sick until
the TCMD goes away. Before, I reported UltraEdit. This time it was a
different TCMD/TCC (V11) tab that stalled until I killed the V12 TCMD.

I started V12 TCMD, which created two V11 TCC tabs. I started a V12 TCC tab and exited out of the V11 tabs, leaving a single V12 TCC in V12 TCMD. No other V12 anything were being used. I minimized that and several hours later went back but couldn't restore TCMD from the task bar back to normal.

This is going to be impossible to diagnose without a reproducible failcase. (It's also going to have to be at least partially due to a bug in Windows, because this is supposed to be impossible in Windows!)

However, I definitely do *not* recommend running TCMD 11 and TCMD 12 simultaneously, as they're going to compete for the same files, shared memory, and semaphores.<O:p</O:p

 

[Steve Fabian]

---- Original Message ----
From: rconn
| However, I definitely do *not* recommend running TCMD 11 and TCMD 12
| simultaneously, as they're going to compete for the same files,
| shared memory, and semaphores.

I presume the counterrecommendation does not apply to multiple instances of TCC, regardless of version, i.e., it is safe to run multiple instances of each of TCC 11 and TCC 12, whether as TCMD tabs or in their private windows.
--
Steve

 

[rconn]

I presume the counterrecommendation does not apply to multiple instances of TCC, regardless of version, i.e., it is safe to run multiple instances of each of TCC 11 and TCC 12, whether as TCMD tabs or in their private windows.

If running TCC standalone, the only interaction will be in the shared lists.

When running in a tab window, (1) there's no reason to run multiple versions, and (2) you'll lose significant functionality, as the interprocess communication between TCC and TCMD is version-specific.