starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Open windows from a previous session" opens wrong tabs after crash #23204

New Issue
Closed
opened 2026-01-31 08:35:17 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:35:17 +00:00
Owner
Copy Link

Originally created by @sparrowt on GitHub (Apr 25, 2025).

Originally assigned to: @lhecker, @carlos-zamora on GitHub.

Windows Terminal version

1.22.10731.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

  1. Run Windows Terminal for several days, over which period many tabs have been opened, closed, renamed etc.
  2. Somehow Windows Terminal crashes (this in itself is obviously caused by a different bug, but inevitably this will sometimes happen)
  3. Re-launch Windows Terminal and find that it has restored the wrong tabs (the ones that were open last time it had a clean shutdown)

Expected Behavior

Windows Terminal should restore the tabs that were open at least vaguely recently before the crash (e.g. by persisting this state either on a regular interval, or each time a new tab is opened/renamed.

Actual Behavior

Instead it restores whatever tabs were open last time I explicitly closed it (i.e. the same set that it restored last time) which may well be multiple days ago and completely different from the tabs that I had been using before the crash.

Unfortunately this makes the restore feature pretty useless in the case of a crash 😢

Originally created by @sparrowt on GitHub (Apr 25, 2025). Originally assigned to: @lhecker, @carlos-zamora on GitHub. ### Windows Terminal version 1.22.10731.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce 1. Run Windows Terminal for several days, over which period many tabs have been opened, closed, renamed etc. 2. Somehow Windows Terminal crashes (this in itself is obviously caused by a _different_ bug, but inevitably this will sometimes happen) 3. Re-launch Windows Terminal and find that it has restored the wrong tabs (the ones that were open last time it had a _clean_ shutdown) ### Expected Behavior Windows Terminal should restore the tabs that were open at least vaguely recently before the crash (e.g. by persisting this state either on a regular interval, or each time a new tab is opened/renamed. ### Actual Behavior Instead it restores whatever tabs were open last time I explicitly closed it (i.e. the same set that it restored last time) which may well be multiple days ago and completely different from the tabs that I had been using before the crash. Unfortunately this makes the restore feature pretty useless in the case of a crash 😢
claunia added the Issue-BugPriority-3Needs-Tag-FixProduct-TerminalArea-Windowing labels 2026-01-31 08:35:18 +00:00
claunia commented 2026-01-31 08:35:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 30, 2025):

Hmmmmmmm. Well, that's not good. Thanks!

@DHowett commented on GitHub (Apr 30, 2025): Hmmmmmmm. Well, that's not good. Thanks!
claunia commented 2026-01-31 08:35:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 30, 2025):

Notes from discussion: maybe we should persist the window layout (cheap) every couple minutes or whatever, but not the buffers yet (too expensive to do serially).

Right now, we only clear the old session off disk when we save a new one. You can well imagine what that means. 🙂

@DHowett commented on GitHub (Apr 30, 2025): Notes from discussion: maybe we should persist the window layout (cheap) every couple minutes or whatever, but not the buffers yet (too expensive to do serially). Right now, we only _clear the old session off disk_ when we save a new one. You can well imagine what that means. 🙂
claunia commented 2026-01-31 08:35:20 +00:00
Author
Owner
Copy Link

@sparrowt commented on GitHub (May 1, 2025):

maybe we should persist the window layout (cheap) every couple minutes or whatever, but not the buffers yet

Thanks yes that would be great - the crucial thing is remembering which set of things I was keeping an eye on and the terminal type + tab title (+ cwd) is much better than nothing. I'm not fussed about the buffers (in fact would be nice to be able to disable that, pretty sure I've seen another ticket for that).

@sparrowt commented on GitHub (May 1, 2025): > maybe we should persist the window layout (cheap) every couple minutes or whatever, but not the buffers yet Thanks yes that would be great - the crucial thing is remembering which set of things I was keeping an eye on and the terminal type + tab title (+ cwd) is much better than nothing. I'm not fussed about the buffers (in fact would be nice to be able to disable that, pretty sure I've seen another ticket for that).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Windowing Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23204
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?