The window has crashed (reason: 'oom', code: '-536870904')

[newtykip]

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

• VS Code Version: 1.59.0
• OS Version: Windows 10 21H1 (Build 19043.1110)

Steps to Reproduce:

1. Launch VS Code
2. Randomly but frequently while working I get the error screenshotted above and when I attempt to re-open the window it just crashes out of VS Code entirely.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• The window has crashed (reason: 'oom') (#126127)

[arzpgh60]

0pen

[newtykip]

This keeps happening still at frequent intervals, it's incredibly strange.

[deepak1556]

Please follow these steps https://github.com/microsoft/vscode/wiki/Native-Crash-Issues and attach the crash log.

[pbldmngz]

Got the exact same issue opening an executable created with pyinstaller that used easyocr. I had a bug that made the program create infinite processes and collapse memory but never work. It works just fine in the editor though. After collapting my sistem this error may appear.

Just for the sake of info: my problem in python was caused for not using PIL -> ImageGrab, I was using other ImageGrab library.

[Voltaicmimic]

I've been getting this problem for the past like 3 days. Not only Visual Studio Code crashes, but Brave (My browser) & Discord crashes too! This is insanely annoying!! I'm just trying to code some JS maaan!

[Zaieon]

I've been getting this same issue also. My Visual Studio totally crashes and I have to re-run. I did an update recently though so I'm guessing that's the cause. Or maybe it has something to do with react because that's the technology I'm working with. Still searching for ways to fix it.

[manish-amplework]

I have also getting this issue.

[Zaieon]

How did you sort this out?

…

On Tue, 31 Aug 2021, 13:23 Manish Balodia, ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/87966718/131501689-80f68b88-ac86-4287-bcec-068ab3a5ce50.png> I have also getting this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#130375 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKSAJIWHJCT4VNDHC5FJPV3T7TCTHANCNFSM5BY7LRFQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[the-one-with-raspberry]

I am also getting this issue!!!

[the-one-with-raspberry]

@newtykins Good thing that you opened the issue

[newtykip]

Oh hey I didn't really find a way to fix it because I had planned to clean install Windows some time soon so I decided to do it then and when I reinstalled Visual Studio Code worked. So maybe fully remove Visual Studio Code from your system and then reinstall it?

[ghartz-hz]

I'm also seeing this problem fairly frequently since the last update of VSCode. On top of that, although a lot more minor of an issue, "Reopen" doesn't do anything.

[f-markus]

I also had / have this issue and I narrowed it down to a very strange change in my extension's package.json:
I do provide custom semantic types, so I have plenty of entries like:

"semanticTokenTypes": [
      {
        "id": "identifier",
        "description": "identifiers without specific role"
      },
      {
        "id": "type",
        "superType": "type"
      },
      {
        "id": "label",
        "superType": "label"
      },
      {
        "id": "attribute"
      },
]

When I added "description": "..." tags to all of the semanticTokenTypes (because otherwise the extension's runtime-status shows a warning that those entries don't have descriptions), the OOM error keeps showing up deterministically. It's not a single entry that causes the problem, but at least three of them. I couldn't figure out a workaround except for removing the "description" tags again. The tokenTypes in question are the ones above: type, label and attribute. I suspect that their name is already in use and this causes some strange behavior of VSCode

[Hashflower]

Same issue here, anyone fixed it ?

[smi48]

same issue, wtf

[Yasi97]

Same issue here, anyone solved it ?

[PaprPrintr]

Solved it, one of my RAM stick was fucked, as soon as I removed it the problem disappeared. Recommend to do a RAM check to identify the default one in case. Might not be the issue, but for me that was it.