microsoft / microsoft/WSL

WSL stops responding and vmmem spikes CPU to 100%

Open
#9,592 56 comments 19 reactions 1 assignee View on GitHub

@OneBlue is already working on this.

Since Feb 6, 2023.

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

Description

Version

Microsoft Windows 10 Version 22H2 (OS Build 19045.2486)

WSL Version
  • WSL 2
  • WSL 1
Kernel Version

5.10.16

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps
  1. Launch WSL
  2. Use it normally (mostly ssh sessions, some git and grep operations, sometimes extracting Android images and copying around 1GB of files).
    (I believe this happens regardless of if I am working with large files, but it may be more frequent in that case. I have had cases where I am not running anything and it still locks up).

I recently upgraded to WSL 1.1.0 per another GitHub issue and this did not resolve the issue.

Expected Behavior

I expect WSL to respond and not use a high percentage of CPU resources. In the rare case where WSL acts up, wsl --shutdown should stop it.

Actual Behavior

I leave WSL running all the time based on my workload. For years, this worked flawlessly. For the last few months, after a day to a few days up and some suspends and resumes, WSL stops respnding, uses 80+% CPU, wsl --shutdown doesn't work, and I cannot get it to work unless I reboot my PC.

Diagnostic Logs

WslLogs-2023-02-05_17-56-42.zip

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.