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

Up to 1 second delay in Windows 11 when launching console apps outside of terminal when Windows Terminal is set as default console host #15829

New Issue
Closed
opened 2026-01-31 04:49:39 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:49:39 +00:00
Owner
Copy Link

Originally created by @pervognsen on GitHub (Nov 9, 2021).

Windows Terminal version (or Windows build number)

10.0.22000.0, 1.12.2931.0

Other Software

No response

Steps to reproduce

I have a win32 console subsystem application, which I normally run directly from a Powershell instance under Windows Terminal. It runs in about 40ms when I measure its running time with Measure-Command. I happened to be profiling this app with a third-party profiler (Superluminal) which made me notice it was spending about 1 second in the Ldr code that's responsible for loading the executable image (and its DLL dependencies).

Essentially all of that 1 second is spent blocked in the ConsoleInitialize call stack. I attached a screenshot so you can see for yourself.

image

I'm on Windows 11 and have Windows Terminal Preview (with the reported version number) set as my default terminal application. If I set the default terminal application back to Windows Console Host, the same Ldr code path only consumes 50ms instead of 1s.

Edit: I did an ETW trace which confirms that the console app is waiting on OpenConsole.exe -> WindowsTerminal.exe.

Edit: I did a bunch more traces and most of them take closer to 300 ms than 1 s. The lower end numbers are less egregious and I probably wouldn't have filed this issue if my initial measurements were in that lower range. In any case, I'll leave this issue here in case you think something here merits investigation.

Expected Behavior

Console applications should start up instantaneously even when launched from outside of terminal.

Actual Behavior

ConsoleInitialize code path takes ~1s to complete.

Originally created by @pervognsen on GitHub (Nov 9, 2021). ### Windows Terminal version (or Windows build number) 10.0.22000.0, 1.12.2931.0 ### Other Software _No response_ ### Steps to reproduce I have a win32 console subsystem application, which I normally run directly from a Powershell instance under Windows Terminal. It runs in about 40ms when I measure its running time with Measure-Command. I happened to be profiling this app with a third-party profiler (Superluminal) which made me notice it was spending about 1 second in the Ldr code that's responsible for loading the executable image (and its DLL dependencies). Essentially all of that 1 second is spent blocked in the ConsoleInitialize call stack. I attached a screenshot so you can see for yourself. ![image](https://user-images.githubusercontent.com/123173/141012490-0962d9b8-cde7-4e43-a8e2-3eeaeb6e2f00.png) I'm on Windows 11 and have Windows Terminal Preview (with the reported version number) set as my default terminal application. If I set the default terminal application back to Windows Console Host, the same Ldr code path only consumes 50ms instead of 1s. Edit: I did an ETW trace which confirms that the console app is waiting on OpenConsole.exe -> WindowsTerminal.exe. Edit: I did a bunch more traces and most of them take closer to 300 ms than 1 s. The lower end numbers are less egregious and I probably wouldn't have filed this issue if my initial measurements were in that lower range. In any case, I'll leave this issue here in case you think something here merits investigation. ### Expected Behavior Console applications should start up instantaneously even when launched from outside of terminal. ### Actual Behavior ConsoleInitialize code path takes ~1s to complete.
claunia commented 2026-01-31 04:49:40 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 10, 2021):

Hey there @pervognsen. Great investigation! You've discovered pretty much exactly what I would have done if I were to trace and profile the route.

You are correct that it is likely waiting on that handoff from OpenConsole.exe to WindowsTerminal.exe. The entire thing is sort of a synchronous block until everyone is ready to start filling their buffers with incoming data.

The 1 second is not great. I'm with you there. 300ms is more reasonable. Either way we look at it, though, since Windows Terminal has "more" going on than the original console host did... it is going to take more time and effort to stand up.

I'm betting that the subsequent launches weren't as bad due to the DLLs needed being hot somewhere in some cache.

Long term, I think what we'll need to work on here is having some portions of the Terminal reside in pre-launch cache and/or work on our idea to have a background service resident and waiting to catch things like the quake mode key (#9996) and perhaps juice up the startup of inbound connections by having things partially already ready to go. We also likely need to continue our work with the XAML team and the Performance teams to work on what we can do to speed up launch. Additionally, we have our Engineering Improvement Month coming up starting next week... and one of my tasks is to look at PGO... including for launch speed. #11688

Hopefully between those things, we'll improve this story more and more over time.

In the meantime... if you need that super fast performance, you'll have to turn the Terminal off as your default application. Though if you do capture any particularly egregious ETL traces, I'd be happy to have them so I can try to identify areas where we can speed up the launch or improve the PGO training.

Thank you for your report.

@miniksa commented on GitHub (Nov 10, 2021): Hey there @pervognsen. Great investigation! You've discovered pretty much exactly what I would have done if I were to trace and profile the route. You are correct that it is likely waiting on that handoff from OpenConsole.exe to WindowsTerminal.exe. The entire thing is sort of a synchronous block until everyone is ready to start filling their buffers with incoming data. The 1 second is not great. I'm with you there. 300ms is more reasonable. Either way we look at it, though, since Windows Terminal has "more" going on than the original console host did... it is going to take more time and effort to stand up. I'm betting that the subsequent launches weren't as bad due to the DLLs needed being hot somewhere in some cache. Long term, I think what we'll need to work on here is having some portions of the Terminal reside in pre-launch cache and/or work on our idea to have a background service resident and waiting to catch things like the quake mode key (#9996) and perhaps juice up the startup of inbound connections by having things partially already ready to go. We also likely need to continue our work with the XAML team and the Performance teams to work on what we can do to speed up launch. Additionally, we have our Engineering Improvement Month coming up starting next week... and one of my tasks is to look at PGO... including for launch speed. #11688 Hopefully between those things, we'll improve this story more and more over time. In the meantime... if you need that super fast performance, you'll have to turn the Terminal off as your default application. Though if you do capture any particularly egregious ETL traces, I'd be happy to have them so I can try to identify areas where we can speed up the launch or improve the PGO training. Thank you for your report.
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-Performance Issue-Question Product-Terminal Resolution-Answered
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#15829
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?