VS Code fails with 'oom' -536870904 when editing bash scripts

[Ben-Voris]

Does this issue occur when all extensions are disabled?: Don't know as I'm unable to work without extensions.

Issue Type: Bug

While editing some small (< 200 lines) bash scripts, VS Code fails with "The window has crashed (reason: 'oom' -536870904). There seems to be no pattern. Sometimes I can edit for days without a failure and sometimes it fails within a few minutes.

I followed the instructions at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues and got two dump files. The attached gziped tar contains the two dumps and the output of https://github.com/nornagon/electron-minidump/blob/master/README.md

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: unavailable_off
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.88GB (6.03GB free)| |Process Argv|--folder-uri file:///c%3A/Users/BVoris/git/shell-setup --crash-reporter-id 485b67da-b4dd-4518-bace-af7b731c74f7| |Screen Reader|no| |VM|0%|

Extensions (24)

Extension|Author (truncated)|Version ---|---|--- Bookmarks|ale|13.2.4 spellright|ban|3.0.62 language-gas-x86|bas|0.0.2 awk-ide-vscode|bea|0.9.0 vscode-markdownlint|Dav|0.47.0 reg|ion|1.0.3 auto-comment-blocks|kev|1.0.1 tal|KNo|0.7.11 sftp|lix|1.12.10 bash-ide-vscode|mad|1.12.1 compare-folders|mos|0.22.2 remote-wsl|ms-|0.66.0 cpptools|ms-|1.9.7 hexeditor|ms-|1.9.5 rech-editor-cobol|rec|1.0.110 vscode-commons|red|0.0.6 vscode-xml|red|0.20.0 vscode-yaml|red|1.6.0 bash-debug|rog|0.3.9 tcl|sle|0.2.0 rewrap|stk|1.16.3 sort-lines|Tyr|1.9.1 x86|whi|0.4.2 clang-format|xav|1.9.0

[bartvanandel]

I'm pretty sure this isn't restricted to bash editing. I run into this multiple times per day, where my npm start terminal (and actually, all other terminals at that point) stop working after they have been open for a while.

Message in 'Log (Main)' at that point:

2022-11-22 10:29:37.631 [error] [uncaught exception in main]: Error: SharedProcess: renderer process gone (detail: oom, code: -536870904)
2022-11-22 10:29:37.631 [error] Error: SharedProcess: renderer process gone (detail: oom, code: -536870904)
    at C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:82:79747
    at w.invoke (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:145)
    at v.deliver (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:2270)
    at g.fire (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:1848)
    at C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:17:20833
    at w.invoke (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:145)
    at v.deliver (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:2270)
    at g.fire (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:19:1848)
    at EventEmitter.<anonymous> (C:\ProgramData\scoop\apps\vscode\1.73.1\resources\app\out\vs\code\electron-main\main.js:79:102213)
    at EventEmitter.emit (node:events:538:35)

I've tried changing the GPU settings for the terminal, but this happens both with GPU acceleration on, with Canvas fallback, and completely off.

This started happening about 4-6 weeks ago, before that I never had this issue.

[deepak1556]

Can you provide a minimal example to repro this issue, thanks!

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!