Tab won't exit after launching browser

[David Marcus]

In a TCC tab in Take Command, I do https://www.imdb.com/title/tt36425792/ . This launches Firefox. I get the usual TCC prompt. I type *exit . Nothing happens. I close Firefox. Then the tab exits.

TCC 36.00.42 x64 Windows 11 [Version 10.0.26200.8328]

 

[vefatica]

I can reproduce that. TCMD must not be elevated.

 

[DieterKoessl]

Same here and a little bit of extra information.

The TCC tab does not hang, if Firefox is already running, that is, when TCC opens an additional tab in Firefox then EXIT works normally.

Edit (one day later):

If you close the tab using Home->Close Tab (or the X on the tab), Firefox gets terminated!

(1) Make sure Firefox is not running
(2) launch any web-page from TCC
(3) wait for browser to appear
(4) in TCMD close TCC using the Home->Close Tab
(5) Firefox closes (probably gets terminated; it later balks about "cannot restore tabs")

 

[rconn]

Fixed in build 43. (Only affected ConPTY tabs.)

 

[DieterKoessl]

Just installed build 45. And no, it is not fixed. See the list in my previous post. If I do this, Firefox gets killed when TCC is closed via TCMD, either "Home->Close" or "X button on Tab"

Just to be clear: "launch any web-page" means "enter any https://... address" and press Enter.

 

[vefatica]

I can still reproduce it with build 45, ConPty and unelevated.

 

[DieterKoessl]

Installed build 48. Now it is working

• Exit closes TCC without hanging
• Closing TCC via TCMD (Home->Close Tab) does not kill Firefox

A very minor nitpick: the internal version number of TCC (36.00.48) and the "version info resource" (30.0.47) of the installer do not match.

 

[vefatica]

Yes, this is better. But ...

It leaves an extra instance of explorer.exe runing. That extra instance terminates after 60 seconds.

 

[rconn]

Yes, this is better. But ...

It leaves an extra instance of explorer.exe runing. That extra instance terminates after 60 seconds.

I have no idea what you mean.

 

[vefatica]

I have no idea what you mean.

Except for the start times, you can see the same info in TaskMgr.

Before:

v:\> tl /f "explorer|firefox|tcmd"
Start  Time             Pid       CPU(s)     WS(M)  Name
--------------------------------------------------------------------------------
05/13  10:26:45.263    2284       42.266     229.3  explorer.exe

After starting TCMD/TCC/ConPty/unelevated and executing https: ... JPSoftForumsURL in TCC, there is a second instance of Explorer which will terminate 60 seconds later.

v:\> tl /f "explorer|firefox|tcmd"
Start  Time             Pid       CPU(s)     WS(M)  Name
--------------------------------------------------------------------------------
05/13  10:26:45.263    2284       42.859     214.8  explorer.exe
05/13  13:35:22.762    2028        1.469     207.8  TCMD.exe
05/13  13:35:33.854    5504        0.234      68.1  explorer.exe
05/13  13:35:34.069    3708        3.375     353.1  firefox.exe
05/13  13:35:34.268    8504        0.844     227.9  firefox.exe
05/13  13:35:34.370    4508        0.031      17.9  firefox.exe
05/13  13:35:34.570    8128        0.375      91.3  firefox.exe
05/13  13:35:34.577    5280        0.141      33.4  firefox.exe
05/13  13:35:34.864    9764        0.484     116.5  firefox.exe
05/13  13:35:35.200    4536        0.047      17.3  firefox.exe
05/13  13:35:35.362    8764        0.078      39.6  firefox.exe

 

[rconn]

WAD, and that's the way Windows works.

TCC in a ConPTY tab cannot use ShellExecute(ex) to launch an URL, because the browser will inherit the pseudoconsole pipe handles, and that will prevent the tab from closing when TCC exits. So it has to use CreateProcess to execute "explorer.exe URL". When you do that with no browser running, Windows starts the browser and after some fairly random period of time explorer.exe will exit, leaving the browser running.

Note that this happens when (1) you run an URL from the command line, (2) don't have a browser running, and (3) leaves a stub of an explorer.exe running for a few seconds. This does not seem like an undue burden on the user, who will never notice it unless they're staring at Task Manager instead of at the browser page they just opened.

 

[vefatica]

Note that this happens when (1) you run an URL from the command line, (2) don't have a browser running, and (3) leaves a stub of an explorer.exe running for a few seconds. This does not seem like an undue burden on the user, who will never notice it unless they're staring at Task Manager instead of at the browser page they just opened.

When done outside TCMD, if there is an extra explorer.exe, it's too short-lived (<1 second) for me to catch. When done inside TCMD, it lives 60 seconds.

 

[rconn]

When done outside TCMD, if there is an extra explorer.exe, it's too short-lived (<1 second) for me to catch. When done inside TCMD, it lives 60 seconds.

Not my doing, and I don't care. (It lives < 30 seconds on my system). You're welcome to complain to Microsoft and demand they change it.

It's also not done in TCMD, it's done in TCC.