Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL runs out of memory when working from a Windows mount #9467

Closed
1 of 2 tasks
ozio85 opened this issue Jan 10, 2023 · 3 comments
Closed
1 of 2 tasks

WSL runs out of memory when working from a Windows mount #9467

ozio85 opened this issue Jan 10, 2023 · 3 comments

Comments

@ozio85
Copy link

ozio85 commented Jan 10, 2023

Version

Microsoft Windows [Version 10.0.19045.2364]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.15.79.1 (rollback option seems to be missing)

Working version:
5.10.102.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

Access many files towards a Windows mount e.g. building from a Git checkout located on the Windows system
The file server that hosts the communication between the WSL system and Windows, will slowly leak memory until it crashes.

Expected Behavior

WSL not to leak memory

Actual Behavior

WSL runs out of memory

Diagnostic Logs

No response

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 17, 2023

/logs

@ghost
Copy link

ghost commented Jan 17, 2023

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

@ghost ghost closed this as completed Jan 24, 2023
@ghost
Copy link

ghost commented Jan 24, 2023

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants