microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.34k stars 28.9k forks source link

Windows 11: VScode crashed (reason: 'oom', code: '-536870904' #226484

Open saviornt opened 1 month ago

saviornt commented 1 month ago

Does this issue occur when all extensions are disabled?: Yes

Steps to Reproduce:

  1. Start writing code.

Attempted Fixes:

  1. Verified that VScode folders are not being uploaded to OneDrive (or any other cloud backup providers)
  2. Deleted all VScode and Project cache files
  3. Deleted VScode backups
  4. Deleted .vscode from App folder
  5. Deleted Windows temp files
  6. Removed all extensions
  7. Excluded VScode from Windows Defender
  8. Verified Large File Optimizations
  9. Changed paging file size from 4096 (Windows auto manage) to 9216 (min) - 196609 (max)
  10. Disabled hardware acceleration

Here is one of the many .dmp files: c0eba4c2-10ff-48ec-94c9-66b49dd2fdfd.dmp

Crash report preview:

EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007fffbb82fabc (KERNELBASE!RaiseException+0x000000000000006c) ExceptionCode: e0000008 ExceptionFlags: 00000081 NumberParameters: 1 Parameter[0]: 0000000000b1b1c7

PROCESS_NAME: Code.exe

ERROR_CODE: (NTSTATUS) 0xe0000008 -

EXCEPTION_CODE_STR: e0000008

EXCEPTION_PARAMETER1: 0000000000b1b1c7

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: code+b55379

MODULE_NAME: Code

IMAGE_NAME: Code.exe

FAILURE_BUCKET_ID: APPLICATION_FAULT_e0000008_Code.exe!Unknown

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 1.92.2.0

FAILURE_ID_HASH: {203dc02c-fd4a-1c4e-3e48-6581c93eb6d2}

moody31415 commented 3 weeks ago

I have started seeing this issue periodically as well. I can't tell if it's an extension leaking, debug window filling up, or something else. I'm guessing it's not a real oom, since when I see the crash dialog my machine has tons of free ram available, (some) vscode process is still running, and none of the vscode specific processes look oversized in task manager. There's no indication of a crash in windows event viewer either. I see this issue happen when I leave my machine for a while / overnight and return to do further work - this hasn't happened to me while actively using VSCode.

Version: 1.93.1 (system setup) Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40 Date: 2024-09-11T17:20:05.685Z Electron: 30.4.0 ElectronBuildId: 10073054 Chromium: 124.0.6367.243 Node.js: 20.15.1 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.22631