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

Buggy title bar appears in focus mode after long uptime #20725

New Issue
Open
opened 2026-01-31 07:22:19 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:22:19 +00:00
Owner
Copy Link

Originally created by @PennRobotics on GitHub (Oct 24, 2023).

Windows Terminal version

1.19.2682.0

Windows build number

10.0.19045.3570

Other Software

No response

Steps to reproduce

  1. Set up focus mode as the default for all sessions.
  2. Run Windows a reasonably long time without restarting
  3. Open a new terminal
  4. Sometimes (even now, not always) a title bar will appear

Expected Behavior

No title bar in focus mode

Actual Behavior

Title bar appears in focus mode—sporadically and after a long system uptime and resource usage.

The window cannot be dragged using the title bar, but the buttons (min/max/close) still function as expected. There are no tabs or text in the title bar.

Currently, I'm at 3:23:14:42 uptime after waking, vmmem was at 5.5 GB. (After the first crash, it is at 3.8 GB.) If I run a handful of wasteful tasks to run up resource usage (e.g. multiple ripgreps in Win command prompt and WSL at the same time) I can exceed 6 GB usage but this doesn't cause the title bar to appear in newly opened terminal processes.

This seems to be a problem independent of profile and other processes. I can run wt cmd and a title bar is there, then wt ubuntu and it's there, then wt powershell and it's no longer there, even though the other terminal processes are still open.

Restarting Windows will restore the expected behavior: no title bar

(update: unrelated to PID stored in a 16-bit variable; problem exists while all PIDs are under 23000)

Originally created by @PennRobotics on GitHub (Oct 24, 2023). ### Windows Terminal version 1.19.2682.0 ### Windows build number 10.0.19045.3570 ### Other Software _No response_ ### Steps to reproduce 1. Set up focus mode as the default for all sessions. 2. Run Windows a reasonably long time without restarting 3. Open a new terminal 4. Sometimes (even now, not always) a title bar will appear <!-- 5. Bonus: "Settings" might appear multiple times in the context (Alt-Space) menu. If you click Settings, the current window plus some (but not all) of the other terminal windows crash. --> ### Expected Behavior No title bar in focus mode ### Actual Behavior Title bar appears in focus mode&mdash;sporadically and after a long system uptime and resource usage. The window cannot be dragged using the title bar, but the buttons (min/max/close) still function as expected. There are no tabs or text in the title bar. <!-- "Settings" will sometimes appear multiple times in the Alt+Space menu, and if I click the ~last~ correct "Settings" menu item, I _will_ get the settings dialog. If I click any other "Settings" menu item, a few terminal windows crash. --> Currently, I'm at 3:23:14:42 uptime after waking, _vmmem_ was at 5.5 GB. (After the first crash, it is at 3.8 GB.) If I run a handful of wasteful tasks to run up resource usage (e.g. multiple ripgreps in Win command prompt and WSL at the same time) I can exceed 6 GB usage but this doesn't cause the title bar to appear in newly opened terminal processes. This seems to be a problem independent of profile and other processes. I can run `wt cmd` and a title bar is there, then `wt ubuntu` and it's there, then `wt powershell` and it's no longer there, even though the other terminal processes are still open. Restarting Windows will restore the expected behavior: no title bar<!--, no extra "Settings" in the context menu. --> (update: unrelated to PID stored in a 16-bit variable; problem exists while all PIDs are under 23000) <!-- I'll also see if I can use something like Spy++ to pick apart which handle/class/etc. is being assigned to those nonworking "Settings" menu items. @PennRobotics - [ ] Spy++ on extra "Settings" menu items - [x] Update second-to-last paragraph with findings -->
claunia added the Issue-BugIn-PRNeeds-Tag-FixProduct-TerminalArea-Windowing labels 2026-01-31 07:22:19 +00:00
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 In-PR Issue-Bug Needs-Tag-Fix 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#20725
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?