wsl2: usage of %LOCALAPPDATA%\Temp\wsl-crashes

[sfoster1]

Host OS: Windows 11 23H2 22631.4169
Guest distribution: ubuntu, kernel 5.15.153.1-microsoft-swandard-WSL2

Something in my WSL environment is causing failed nodejs commands to write crash dumps to %LOCALAPPDATA%\Temp\wsl-crashes in the host fs. This is annoying because I have a lot of RAM and the crash dumps are big, and Windows gives me notifications that my disk space is running low.

I've searched for information about this, but the documentation about crash dumps refers to WSL2 subsystem crashes, and these are crash dumps from command line programs running in the guest OS.

I would like to be able to disable this behavior or relocate the directory where the crash dumps live. Is this possible? Could it be possible? Is there documentation that I am missing?

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• 2.2GB wsl-crash files keep being generated (#12032), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[sfoster1]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

* [2.2GB wsl-crash files keep being generated (#12032)](https://github.com/microsoft/WSL/issues/12032),  similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[sfoster1]

#12032 is definitely the cause of the files that I'm seeing, but the thing I would like is the ability to change where they are written or disable them being written to the host FS.

[OneBlue]

@sfoster1: You can disable crash dump collection by setting:

[wsl2]
MaxCrashDumpCount=-1

In %USERPROFILE%/.wslconfig. After WSL restarts, this will completely disable crash dump collection.