WT disappears after 3 days!? #19606

@vefatica commented on GitHub (Mar 29, 2023):

If you mean this,

"Terminal.wprp" not clickable.

@vefatica commented on GitHub (Mar 29, 2023): If you mean this, ![image](https://user-images.githubusercontent.com/61856645/228678987-d442f682-5b16-4ed4-9d93-4709f03c7284.png) "Terminal.wprp" not clickable.

claunia commented

@DHowett commented on GitHub (Mar 30, 2023):

CLICK THIS

It is the universally accepted icon for "download".

@DHowett commented on GitHub (Mar 30, 2023): CLICK THIS <img width="33" alt="image" src="https://user-images.githubusercontent.com/189190/228689311-1579da64-fbe6-4c73-b110-2ef3a1b1be93.png"> It is the universally accepted icon for "download".

claunia commented

@vefatica commented on GitHub (Mar 30, 2023):

Apparently I'm not seeing what you're seeing.

@vefatica commented on GitHub (Mar 30, 2023): Apparently I'm not seeing what you're seeing. ![image](https://user-images.githubusercontent.com/61856645/228699623-86c81411-7599-4254-91d4-62c829656c22.png)

claunia commented

@DHowett commented on GitHub (Mar 30, 2023):

What on earth?!

Okay, for now, uh... click on "Raw", and use Ctrl+S

I think I'm going crazy! Sorry! :)

@DHowett commented on GitHub (Mar 30, 2023): _What on earth?!_ Okay, for now, uh... click on "Raw", and use <kbd>Ctrl+S</kbd> I think I'm going crazy! Sorry! :)

claunia commented

@vefatica commented on GitHub (Mar 30, 2023):

That just downloads Terminal.wprp.txt with the XML in it.

@vefatica commented on GitHub (Mar 30, 2023): That just downloads Terminal.wprp.txt with the XML in it.

claunia commented

@DHowett commented on GitHub (Mar 30, 2023):

Then rename it! You're the one who thought injecting a remote thread into Explorer to set environment variables was a good plan - I know you can handle a little XML file with the wrong extension! 😁

@DHowett commented on GitHub (Mar 30, 2023): Then rename it! You're the one who thought injecting a remote thread into Explorer to set environment variables was a good plan - I know you can handle a little XML file with the wrong extension! 😁

claunia commented

@vefatica commented on GitHub (Mar 30, 2023):

I know epsilon about XML and obviously even less about exactly what's supposed to happen here. Rename it what? And then what?

@vefatica commented on GitHub (Mar 30, 2023): I know epsilon about XML and obviously even less about exactly what's supposed to happen here. Rename it what? And then what?

claunia commented

@vefatica commented on GitHub (Mar 30, 2023):

OK. I think I have this figured out. Will this (below) work?

Wait until the expected disappearance of WT is imminent That's now somewhat less than 3 days.

wpr -start v:\Terminal.wprp!Terminal.Verbose

After WT has disappeared ...

wpr -stop terminal-trace.etl

zip the ETL file and post/send it.

@vefatica commented on GitHub (Mar 30, 2023): OK. I think I have this figured out. Will this (below) work? Wait until the expected disappearance of WT is imminent That's now somewhat less than 3 days. wpr -start v:\Terminal.wprp!Terminal.Verbose After WT has disappeared ... wpr -stop terminal-trace.etl zip the ETL file and post/send it.

claunia commented

@DHowett commented on GitHub (Mar 30, 2023):

That'll work for us! Thanks, and sorry about the download confusion.

@DHowett commented on GitHub (Mar 30, 2023): That'll work for us! Thanks, and sorry about the download confusion.

claunia commented

@vefatica commented on GitHub (Mar 30, 2023):

And I apologize for being slow to figure it out. At first I thought I would be downloading the WPR tool. Then I found it here already and figured out that I only needed the XML.

I'm also new to PerfView, just learned of it yesterday. Should I be able to view a trace, made as described above, with PerfView? I have symbols (maintained by WinDbg).

@vefatica commented on GitHub (Mar 30, 2023): And I apologize for being slow to figure it out. At first I thought I would be downloading the WPR tool. Then I found it here already and figured out that I only needed the XML. I'm also new to PerfView, just learned of it yesterday. Should I be able to view a trace, made as described above, with PerfView? I have symbols (maintained by WinDbg).

claunia commented

@vefatica commented on GitHub (Apr 1, 2023):

Right on schedule, WT disappeared 3 days after it was started. Here's a bit of a transcript. The zipped ETL file is attached but, to be honest, it doesn't look very interesting. I started the trace about 10 minutes before the disappearance. In the last three days my w32tmsvc added 2.5 seconds to the system clock, explaining, I reckon, the difference between 3 days and the observation below.

v:\> wpr -start v:\Terminal.wprp!Terminal.Verbose

v:\> set pid=%@wmi[.,"select processid from Win32_Process where Caption='windowsterminal.exe'"] & echo Start: %@wmitcvt[%@wmi[.,
"select CreationDate from Win32_Process where ProcessId=%pid"],T] & wait /p %pid & echo Stop:  %_date %_t9
Start: 2023-03-29 11:42:42.788
Stop:  2023-04-01 11:42:45.373

v:\> wpr -stop terminal-trace.etl

v:\> zip disappear.zip terminal-trace.etl
<= V:\terminal-trace.etl

disappear.zip

@vefatica commented on GitHub (Apr 1, 2023): Right on schedule, WT disappeared 3 days after it was started. Here's a bit of a transcript. The zipped ETL file is attached but, to be honest, it doesn't look very interesting. I started the trace about 10 minutes before the disappearance. In the last three days my w32tmsvc added 2.5 seconds to the system clock, explaining, I reckon, the difference between 3 days and the observation below. ``` v:\> wpr -start v:\Terminal.wprp!Terminal.Verbose v:\> set pid=%@wmi[.,"select processid from Win32_Process where Caption='windowsterminal.exe'"] & echo Start: %@wmitcvt[%@wmi[., "select CreationDate from Win32_Process where ProcessId=%pid"],T] & wait /p %pid & echo Stop: %_date %_t9 Start: 2023-03-29 11:42:42.788 Stop: 2023-04-01 11:42:45.373 v:\> wpr -stop terminal-trace.etl v:\> zip disappear.zip terminal-trace.etl <= V:\terminal-trace.etl ``` [disappear.zip](https://github.com/microsoft/terminal/files/11129977/disappear.zip)

claunia commented

@vefatica commented on GitHub (Apr 2, 2023):

Solved! "Stop the task if it runs longer than 3 days" is a default setting of Task Scheduler which I never paid much attention to. I typically start WT via an AutoHotKey script executing u:\schtasksw.exe /run /tn wtelevated. Schtasksw.exe is a GUI version of schtasks.exe (made with editbin.exe) and the "wtelevated" task is on-demand with highest privileges. Starting WT in this way avoids the UAC prompt. Sorry about the false alarm.

I'm still curious. Did terminal-trace.etl work as expected? ... have anything in it about what WT was doing?

@vefatica commented on GitHub (Apr 2, 2023): Solved! "Stop the task if it runs longer than 3 days" is a default setting of Task Scheduler which I never paid much attention to. I typically start WT via an AutoHotKey script executing `u:\schtasksw.exe /run /tn wtelevated`. Schtasksw.exe is a GUI version of schtasks.exe (made with editbin.exe) and the "wtelevated" task is on-demand with highest privileges. Starting WT in this way avoids the UAC prompt. Sorry about the false alarm. I'm still curious. Did terminal-trace.etl work as expected? ... have anything in it about what WT was doing?

claunia commented

@zadjii-msft commented on GitHub (Apr 4, 2023):

Well, that's wild, but a good new thing to learn about!

The .etl did work perfectly fine. From what's in there, it looks like the Terminal was doing... nothing. Not processing any data, not opening new tabs or anything, just hanging out. There was a few events for the regularly scheduled "let's make sure we persist all the window positions" thread, but really nothing else interesting. Nothing in there would indicate a crash, but that's cause it didn't, so neato!

Thanks for following up!

@zadjii-msft commented on GitHub (Apr 4, 2023): Well, that's wild, but a good new thing to learn about! The .etl did work perfectly fine. From what's in there, it looks like the Terminal was doing... nothing. Not processing any data, not opening new tabs or anything, just hanging out. There was a few events for the regularly scheduled "let's make sure we persist all the window positions" thread, but really nothing else interesting. Nothing in there would indicate a crash, but that's cause it _didn't_, so neato! Thanks for following up!

claunia commented