starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Classic Command Prompt consumes high CPU on long log stream #13638

New Issue
Closed
opened 2026-01-31 03:47:58 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:47:58 +00:00
Owner
Copy Link

Originally created by @brunoborges on GitHub (Apr 26, 2021).

Windows Build Number

Windows 10

Processor Architecture

x64

Memory

16 GB

Storage Type, free / capacity

SSD 512 GB

Relevant apps installed

Command Prompt

Traces collected via Feedback Hub

https://github.com/microsoft/java-wdb/issues/23

Isssue description

"if I run a maven build in a cmd window it seems that screen output eats more CPU than the actual build."

https://github.com/microsoft/java-wdb/issues/23

Steps to reproduce

Build a Java project that will produce significant amount of build log.

Example: https://github.com/spring-projects/spring-boot

Expected Behavior

Low CPU.

Actual Behavior

High CPU.

Originally created by @brunoborges on GitHub (Apr 26, 2021). ### Windows Build Number Windows 10 ### Processor Architecture x64 ### Memory 16 GB ### Storage Type, free / capacity SSD 512 GB ### Relevant apps installed Command Prompt ### Traces collected via Feedback Hub https://github.com/microsoft/java-wdb/issues/23 ### Isssue description "if I run a maven build in a cmd window it seems that screen output eats more CPU than the actual build." https://github.com/microsoft/java-wdb/issues/23 ### Steps to reproduce Build a Java project that will produce significant amount of build log. Example: https://github.com/spring-projects/spring-boot ### Expected Behavior Low CPU. ### Actual Behavior High CPU.
claunia commented 2026-01-31 03:48:00 +00:00
Author
Owner
Copy Link

@AvriMSFT commented on GitHub (Apr 27, 2021):

Hey Bruno! I'm gonna move this issue to Windows Terminal's repo :) They own the code for the classic cmd prompt.

@AvriMSFT commented on GitHub (Apr 27, 2021): Hey Bruno! I'm gonna move this issue to Windows Terminal's repo :) They own the code for the classic cmd prompt.
claunia commented 2026-01-31 03:48:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2021):

@brunoborges Could you be more specific as to which build of Windows 10 you're using? Conhost has had a lot of updates over the last 6 years of Windows 10, with a lot of perf improvements along the way.

Are you using the legacy console?
image

@zadjii-msft commented on GitHub (Apr 27, 2021): @brunoborges Could you be more specific as to which build of Windows 10 you're using? Conhost has had a lot of updates over the last 6 years of Windows 10, with a lot of perf improvements along the way. Are you using the legacy console? ![image](https://user-images.githubusercontent.com/18356694/116310962-4920e380-a770-11eb-9800-f075e5fe499a.png)
claunia commented 2026-01-31 03:48:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 27, 2021):

For the record, OP in that reddit thread mentioned

Please note that I'm using Windows 7 so maybe some issues are already improved. Also my issues may stem from my way of doing things and there might be better ways.

And yea, the console host has gotten an enormous amount of investment since Windows 7. I'm dangerously close to just closing this as "Fix-Available" 😄

@zadjii-msft commented on GitHub (Apr 27, 2021): For the record, OP in that reddit thread mentioned > Please note that I'm using Windows 7 so maybe some issues are already improved. Also my issues may stem from my way of doing things and there might be better ways. And _yea_, the console host has gotten an enormous amount of investment since Windows 7. I'm dangerously close to just closing this as "Fix-Available" 😄
claunia commented 2026-01-31 03:48:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 27, 2021):

Sorry, are you reporting an issue from somebody who's running Windows 7? ☹️

@DHowett commented on GitHub (Apr 27, 2021): Sorry, are you reporting an issue from somebody who's running Windows 7? ☹️
claunia commented 2026-01-31 03:48:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 1, 2021):

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 (May 1, 2021): 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**.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity Product-Conhost
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#13638
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?