Terminal crashes/closes/terminates after being idle for a while
ajhindle opened this issue · comments
Windows Terminal version
1.15.3466.0
Windows build number
10.0.22621.0
Other Software
Ubuntu 20.04.5 LTS
Powershell 5.1.22621.963
Steps to reproduce
Leave Terminal running idle for 1+ hours.
EDIT: This can also involve putting the computer to sleep for 1+ hours.
Expected Behavior
Terminal stays on for as long as I want it to
Actual Behavior
It shuts down by itself after 1+ hours running idle.
This didn't happen when I first started using Terminal about 18 months ago. I have upgraded to Windows 11 during that time - is it a coincidence?
The shutdown behaviour is annoying because I didn't tell it to shut down and I lose any work/environment I had running in Terminal.
This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?
If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a .dmp of the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?
If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a
.dmpof the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
hello~ I'm facing the same issue, and tried sereval methods from #12513 , but no lucky. i also set up crash dumps and got some .dmp files. em, how can i send the zipped dmp file to you guys~
@clor09 There are some instructions on how to send the dmp files here: #14025 (comment).
@j4james @zadjii-msft Thx, i uploaded the dmp file here: https://aka.ms/AAj7lag
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
Have some problem with:
Windows 11 22621.1105
Windows Terminal Version: 1.15.3466.0
This sounds a lot like #12513. Can you check your "Background App Permissions" settings/?
If that doesn't seem to fix it, can you try following the steps in this post to set up automatic crash dumps? (For more info, see this link) If that works, then you should be able to automatically get a
.dmpof the terminal when it crashes. Then, can you zip that dump up and send it to us, so we can investigate? Thanks!
I looked at background app permissions and changed it "always" for Terminal - it was set to "power optimised".
Unfortunately that didn't work. I will get the dump files.
UPDATE 23-01-2023: so far I haven't had any dump files appear after several crashes/unsolicited terminations of Terminal.
UPDATE 25-01-2023: WER is still not producing any dump files for Terminal for me. It did give a dump file for RuntimeBroker so at least I know WER is working. Also I have noticed the same crashing/self-terminating behaviour for other Windows apps such as Calculator and Snipping Tool - both of those are still set to "power optimised" battery settings.
Thanks for the report. We're tracking this internally with MSFT-42831529.
Terminal instance auto terminates when the system goes to sleep. Observed in ver. 1.16.10262.0 Kindly fix this issue at the earliest.
Windows version - 10.0.22621.1194
You know what, we've actually got a better dupe in /dup #12513. That's got links to a pile of internal bugs. Thanks!
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!