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

Lag when opening #17799

New Issue
Closed
opened 2026-01-31 05:53:47 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 05:53:47 +00:00
Owner
Copy Link

Originally created by @Leohige on GitHub (Jun 24, 2022).

Windows Terminal version

1.13.11432.0

Windows build number

10.0.22000.0

Other Software

Fresh Windows 11 Install

Steps to reproduce

Open Terminal

Expected Behavior

Open smoothly

Actual Behavior

Takes 5 seconds to open, the window is frozen

image

Originally created by @Leohige on GitHub (Jun 24, 2022). ### Windows Terminal version 1.13.11432.0 ### Windows build number 10.0.22000.0 ### Other Software Fresh Windows 11 Install ### Steps to reproduce Open Terminal ### Expected Behavior Open smoothly ### Actual Behavior Takes 5 seconds to open, the window is frozen ![image](https://user-images.githubusercontent.com/7697524/175658665-eee8a679-f939-416f-a419-8129a8d369ea.png)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:53:47 +00:00
claunia commented 2026-01-31 05:53:48 +00:00
Author
Owner
Copy Link

@Leohige commented on GitHub (Jun 25, 2022):

I don't know why, but it seems to be related to Alienware Command Center software.

If it's installed the terminal always froze, even with a windows 11 fresh install.

https://www.dell.com/support/home/pt-br/drivers/driversdetails?driverid=1nn4h

@Leohige commented on GitHub (Jun 25, 2022): I don't know why, but it seems to be related to Alienware Command Center software. If it's installed the terminal always froze, even with a windows 11 fresh install. https://www.dell.com/support/home/pt-br/drivers/driversdetails?driverid=1nn4h
claunia commented 2026-01-31 05:53:48 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 27, 2022):

If it only occurs when the Alienware Command Center software is installed, is it still a bug in Windows Terminal? 🤔
Does the Terminal (or maybe any other application) use a lot of CPU during those 5 seconds?

@lhecker commented on GitHub (Jun 27, 2022): If it only occurs when the Alienware Command Center software is installed, is it still a bug in Windows Terminal? 🤔 Does the Terminal (or maybe any other application) use a lot of CPU during those 5 seconds?
claunia commented 2026-01-31 05:53:48 +00:00
Author
Owner
Copy Link

@Leohige commented on GitHub (Jun 28, 2022):

If it only occurs when the Alienware Command Center software is installed, is it still a bug in Windows Terminal? 🤔 Does the Terminal (or maybe any other application) use a lot of CPU during those 5 seconds?

The CPU usage stays 5 - 10% when opening terminal, nothing else gets frozen when terminal is opening too

@Leohige commented on GitHub (Jun 28, 2022): > If it only occurs when the Alienware Command Center software is installed, is it still a bug in Windows Terminal? 🤔 Does the Terminal (or maybe any other application) use a lot of CPU during those 5 seconds? The CPU usage stays 5 - 10% when opening terminal, nothing else gets frozen when terminal is opening too
claunia commented 2026-01-31 05:53:49 +00:00
Author
Owner
Copy Link

@linuxlc commented on GitHub (Jul 25, 2022):

I met same problem since WT 1.13 (1.12 is ok, 1.14 just like 1.13) on win10 (currently I'm using 10.0.19043.1826).
It happens not only when opening wt.exe, all the operations (Like "open a new tab", "duplicate tab", "split tab") to create a "OpenConsole.exe" subprocess can trigger the problem.
Cpu usage seems OK just like @Leohige 's observation.
Btw, I don't have Alienware Command Center installed.

@linuxlc commented on GitHub (Jul 25, 2022): I met same problem since WT 1.13 (1.12 is ok, 1.14 just like 1.13) on win10 (currently I'm using 10.0.19043.1826). It happens not only when opening wt.exe, all the operations (Like "open a new tab", "duplicate tab", "split tab") to create a "OpenConsole.exe" subprocess can trigger the problem. Cpu usage seems OK just like @Leohige 's observation. Btw, I don't have Alienware Command Center installed.
claunia commented 2026-01-31 05:53:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches.

1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561)

@zadjii-msft commented on GitHub (Jul 25, 2022): If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches. 1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561)
claunia commented 2026-01-31 05:53:49 +00:00
Author
Owner
Copy Link

@linuxlc commented on GitHub (Jul 27, 2022):

If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches.

1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561)

@zadjii-msft Thanks for the help. Problem solved, it's antivirus delaying wt.exe/windowsterminal.exe/openconsole.exe.
Transparent window frame happens very fast so it's ok with me.

@linuxlc commented on GitHub (Jul 27, 2022): > If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches. > > 1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561) @zadjii-msft Thanks for the help. Problem solved, it's antivirus delaying wt.exe/windowsterminal.exe/openconsole.exe. Transparent window frame happens very fast so it's ok with me.
claunia commented 2026-01-31 05:53:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 31, 2022):

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.

@ghost commented on GitHub (Jul 31, 2022): 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**.
claunia commented 2026-01-31 05:53:49 +00:00
Author
Owner
Copy Link

@Leohige commented on GitHub (Aug 1, 2022):

If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches.

1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561)

I'm not using antivirus, only windows defender by default. But i'm using transparent background

@Leohige commented on GitHub (Aug 1, 2022): > If it's not Alienware Command Center, then maybe there's something else that's delaying the boot of OpenConsole.exe. Y'all have any sort of antivirus installed? Maybe there's an overzealous A/V that's scanning OpenConosle.exe every time it launches. > > 1.13 was the first version that had the transparent window backdrop, which is what's causing the transparent window frame here. Before that, then the window would have appeared with probably a black BG, until the first tab loaded. Did the same delay happen on 1.12, but with a solid window instead of a transparent one/? (that's tracked over in #11561) I'm not using antivirus, only windows defender by default. But i'm using transparent background
claunia commented 2026-01-31 05:53:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 1, 2022):

Yea, I'm gonna reckon that this is just /dup #11561. Before that release, the Terminal opened with a solid BG, which at least looked sensible. Now it looks a little more insane. Thanks!

@zadjii-msft commented on GitHub (Aug 1, 2022): Yea, I'm gonna reckon that this is just /dup #11561. Before that release, the Terminal opened with a solid BG, which at least looked sensible. Now it looks a little more insane. Thanks!
claunia commented 2026-01-31 05:53:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 1, 2022):

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!

@ghost commented on GitHub (Aug 1, 2022): 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!
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 Issue-Bug Resolution-Duplicate
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#17799
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?