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

Starting WSL Ubuntu20.04 from Windows Terminal will cause high CPU usage of init process #17202

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

Originally created by @moyrne on GitHub (Apr 9, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

21H2 19044.1586

Other Software

Starting WSL Ubuntu20.04 from Windows Terminal will cause high CPU usage of init process. Starting from WSL with the command wsl -d Ubuntu-20.04 will not have this problem

WSL1
Ubuntu-20.04

$ unmae -a
Linux DESKTOP-Q3G0PTO 4.4.0-19041-Microsoft #1237-Microsoft Sat Sep 11 14:32:00 PST 2021 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce

  • config: command line: wsl.exe -d Ubuntu-20.04

  • Start Windows Terminal and open Ubuntu-20.04

Expected Behavior

The CPU usage of the init process is less than 10%

Actual Behavior

The init process continues to occupy 100%

Originally created by @moyrne on GitHub (Apr 9, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 21H2 19044.1586 ### Other Software Starting WSL Ubuntu20.04 from Windows Terminal will cause high CPU usage of init process. Starting from WSL with the command `wsl -d Ubuntu-20.04` will not have this problem WSL1 Ubuntu-20.04 $ unmae -a Linux DESKTOP-Q3G0PTO 4.4.0-19041-Microsoft #1237-Microsoft Sat Sep 11 14:32:00 PST 2021 x86_64 x86_64 x86_64 GNU/Linux ### Steps to reproduce - config: command line: `wsl.exe -d Ubuntu-20.04` - Start Windows Terminal and open Ubuntu-20.04 ### Expected Behavior The CPU usage of the init process is less than 10% ### Actual Behavior The init process continues to occupy 100%
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:35:17 +00:00
claunia commented 2026-01-31 05:35:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 11, 2022):

What is the startingDirectory for your WSL profile set to? This sounds a lot like #12343

@zadjii-msft commented on GitHub (Apr 11, 2022): What is the `startingDirectory` for your WSL profile set to? This sounds a lot like #12343
claunia commented 2026-01-31 05:35:18 +00:00
Author
Owner
Copy Link

@moyrne commented on GitHub (Apr 11, 2022):

What is the startingDirectory for your WSL profile set to? This sounds a lot like #12343

After I set the "startingdirectory":"\\\\wsl$\\ubuntu-20.04\\home\\username" according to #12343, the init process dose not have 100%. There is usename/dir1 in my directory, which is a soft link. After setting \\\\wsl$\\ubuntu-20.04\\home\\username\\dir1, you will be prompted that the directory name is invalid

目录名称无效。

[已退出进程，代码为 4294967295 (0xffffffff)]）

How can I set the default to enter this directory?

@moyrne commented on GitHub (Apr 11, 2022): > What is the `startingDirectory` for your WSL profile set to? This sounds a lot like #12343 After I set the `"startingdirectory":"\\\\wsl$\\ubuntu-20.04\\home\\username"` according to #12343, the init process dose not have 100%. There is `usename/dir1` in my directory, which is a soft link. After setting `\\\\wsl$\\ubuntu-20.04\\home\\username\\dir1`, you will be prompted that the directory name is invalid ~~~ 目录名称无效。 [已退出进程，代码为 4294967295 (0xffffffff)]） ~~~ How can I set the default to enter this directory?
claunia commented 2026-01-31 05:35:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 11, 2022):

Presumably, the soft link in WSL isn't an actual path on the Windows OS side, so creating a process at that path is gonna fail, since the Windows side can't resolve that.

I'd try manually passing in the resolved path for that soft link. Like, if /home/username/dir1 -> /etc/foo/bar, then set the startingDirectory to \\\\wsl$\\ubuntu-20.04\\etc\\foo\\bar

/dup #12343

@zadjii-msft commented on GitHub (Apr 11, 2022): Presumably, the soft link in WSL isn't an actual path on the Windows OS side, so creating a process at that path is gonna fail, since the Windows side can't resolve that. I'd try manually passing in the resolved path for that soft link. Like, if `/home/username/dir1 -> /etc/foo/bar`, then set the `startingDirectory` to `\\\\wsl$\\ubuntu-20.04\\etc\\foo\\bar` /dup #12343
claunia commented 2026-01-31 05:35:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 11, 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 (Apr 11, 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#17202
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?