2.2GB wsl-crash files keep being generated

[nickchomey]

Windows Version

Microsoft Windows [Version 10.0.22635.4145]

WSL Version

2.3.17.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

I have no idea.

Expected Behavior

For this to not happen

Actual Behavior

2.2GB wsl-crash files keep getting generated and I have no idea what might be causing it. I haven't even noticed any crashes happening.

When I clear them, they just come back soon enough. It seems like it stops when it has exhausted my disk space.

Diagnostic Logs

No response

[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 [email protected] 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!

Open similar issues:

• WSL crashes and can't be restarted (#9767), similarity score: 0.72
• WSL2 reliably crashes when handling files > 10GB (#5410), similarity score: 0.72

Closed similar issues:

• WSL2 (Ubuntu) has partially deleted itself twice (#8876), similarity score: 0.74
• WSL2 VM crashes and starts using all available host memory (#7215), similarity score: 0.70

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

[nickchomey]

Here's the log files. I just started and stopped it immediately to collect system info, because there isn't any particular action that seems to cause this.

WslLogs-2024-09-13_13-27-23.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.17.0

[zcobol]

The clue is in the filename vscode-server-bin. Open one of the files with windbg and explore further what's causing the crash. Or, try reinstalling the vscode-server in your WSL instance by deleting ~/.vscode-server-bin folder.

On my system there are two dumps at this time, one caused by sytemd-journald and the other by systemd-logind:

-a---           9/11/2024  9:41 PM       10014720 wsl-crash-1726116080-36-_usr_lib_systemd_systemd-journald-6.dmp
-a---           9/11/2024 10:18 PM        1548288 wsl-crash-1726118327-96-_usr_lib_systemd_systemd-logind-6.dmp

[nickchomey]

Thank you! That didnt turn up much information (libc_so was the only clue), but I think I've traced the issue to the Intelephense vscode extension, which doesn't seem to handle having many php projects open in the same workspace very well. I'll close this now.