feat(wsl): cap WSL2 maxCrashDumpCount to prevent disk exhaustion#722
Conversation
Updates `.wslconfig` generation to include `maxCrashDumpCount=3` in the `[wsl2]` section. This bounds the number of retained WSL2 crash dumps (e.g., from Electron/renderer processes) to 3, mitigating the risk of host C: drive exhaustion during persistent crash-loop scenarios. Co-authored-by: mkobit <1447148+mkobit@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Updates
.wslconfiggeneration to includemaxCrashDumpCount=3in the[wsl2]section. This bounds the number of retained WSL2 crash dumps (e.g., from Electron/renderer processes) to 3, mitigating the risk of host C: drive exhaustion during persistent crash-loop scenarios.PR created automatically by Jules for task 10228478054954523579 started by @mkobit