microsoft / microsoft/WSL

Show Linux processes in Task manager

Open
#6,881 14 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

Is your feature request related to a problem? Please describe.

Sometimes my computer is slow, and I'd like to be able to see what's slowing it down, so I start Task Manager.

If a Linux process is slowing my machine down or using too many resources, I won't be able to see it in Task Manager. Instead I have to run an additional process inside the Linux VM (which may not even execute in a reasonable amount of time if the Linux VM is busy) to see what the process is.

Describe the solution you'd like

Microsoft Edge already reports usage of individual tabs to Task Manager:
image

It would be useful for the agent that runs in WSL2 to report the same details, allowing individual WSL2 processes to show up similar to how Edge tabs are.

Eg, say if my 'next.js' build process has a memory leak, I should be able to find and stop the process from Task Manager.

WSL1 already showed Linux processes, according to Rich Turner, so this could be looked at in some ways as a regression (though obviously WSL2 and WSL1 have very different architectures).

Describe alternatives you've considered

Right now I just have to see it's not a Windows process in Task Manager, jump into the Linux VM and wait for htop or top or similar to start

Additional context

None. Thanks for WSL2 thought it's great! 🙂

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how the WSL2 agent exposes process and resource data to Windows Task Manager, and compare that behavior with WSL1. Done means individual WSL2 processes are visible in Task Manager with enough detail to identify and stop them.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.