Dave

This would also reduce the likelihood of merge conflicts, because new words from two different branches are less likely to end up in the same place (i.e. at the end...

Hi @FernandoMiguel, are you able to post the output of the GitWebLinks window (you can obfuscate any file paths if you want to).

Sorry, I left a word out. I meant the GitWebLinks _output_ window. 

This has happened before in #443 and #500. The latest version of VS Code updated Electron and Node, which breaks this extension. https://code.visualstudio.com/updates/v1_69#_electron-18-update

VS Code updated to Electron 22 and this bug is now happening again. https://code.visualstudio.com/updates/v1_78#_electron-22-update Version: 1.78.0 (user setup) Commit: 252e5463d60e63238250799aef7375787f68b4ee Date: 2023-05-03T20:09:00.748Z Electron: 22.4.8 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0...

@andrewbranch Any ideas why 385db449f5395ab4d8f24c5f531e85aebbe228c7 might have triggered this issue?

> Because we’re loading more of your own JS files I understand that more files need to be loaded and that will lead to more memory usage, but _6,000 MB_...

Unfortunately, the extended diagnostics from `tsc --extendedDiagnostics` are virtually identical because the issue doesn't occur when compiling via `tsc`. It only occurs when using a "watch compiler host". | Property...

@andrewbranch Here are the extended diagnostics from the watch host compiler for 5.3.3 and 5.4.5: | Property | v5.3.3 | v5.4.5 | Diff | Diff % | | ------------------------- |...

Apologies for the slow response. I've discovered an important piece of information. This only happens on Windows. I was able to set up a WSL environment with the same projects...