All running Visual Studio code instances shutdown all at once

[miladelecancy]

I'm currently working on a relatively heavy project. project has at least 15 uServices ( all in nodejs) a angular5 front. all instances are opened using visual studio code. usually when I start working on angular side suddenly all running instances are shutdown. I wonder is it a bug or some thing is wrong with my machine by the way.
Thanks.

• VSCode Version: 1.22.2
• OS Version: Win 10.0.17134.1 (x64)
• CPU: CoreI7 2600k - 3.4GHz
• RAM: 32GB DDR3

Steps to Reproduce:

1. Running all instances.
2. Nodemon and ng serve are running in VSCode terminal.
3. Working on angular cause all processes to shutdown.

Does this issue occur when all extensions are disabled? Yes

[miladelecancy]

Just a brief update.

• I run node uServices out of VSCode terminal. Still the problem exists. So it has nothing to do with terminal.
• Also i like to mention it has nothing to do with Angular. because this time it was happened during working with NodeJs side.
• I wonder is it because of many instances running?
• One very important thing that I've forget to mention. It was happening earlier during working with PhpStorm and WebStorm. Both of them had this problem. I even format and install a fresh new OS for this. but still it's there... .

[Tyriar]

@miladelecancy could you close all windows and see if it reproduces when you launch the first window using code --verbose --disable-extensions? If the close does happen could you check the terminal for output on the close event?

[miladelecancy]

OK @Tyriar . It seems other VSC instances are sending their output to first initiated one. by the way it's first output: ( there was no closing at startup phase).

[20700:0530/115336.220:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[main 11:53:36 AM] Starting VS Code
[main 11:53:36 AM] from: m:\Apps\Code\Microsoft VS Code\resources\app
[main 11:53:36 AM] args: { _: [],
help: false,
h: false,
version: false,
v: false,
wait: false,
w: false,
diff: false,
d: false,
add: false,
a: false,
goto: false,
g: false,
'new-window': false,
n: false,
'unity-launch': false,
'reuse-window': false,
r: false,
'open-url': false,
performance: false,
p: false,
'prof-startup': false,
verbose: true,
logExtensionHostCommunication: false,
'disable-extensions': true,
disableExtensions: true,
'list-extensions': false,
'show-versions': false,
nolazy: false,
issue: false,
'skip-getting-started': false,
'skip-release-notes': false,
'sticky-quickopen': false,
'disable-restore-windows': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-crash-reporter': false,
'skip-add-to-recently-opened': false,
status: false,
s: false,
'file-write': false,
'file-chmod': false }
[main 11:53:36 AM] Resolving machine identifier...
[main 11:53:36 AM] Resolved machine identifier: 8ef49aebf1b3c60da09cb79ad446c100fbcb7600610ce0351932b450c01a0185
[main 11:53:36 AM] update#setState idle
[20700:0530/115338.222:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] windowsService#whenSharedProcessReady
[20700:0530/115338.255:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115338.271:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] windowsService#startCrashReporter
[main 11:53:38 AM] windowsService#setRepresentedFilename 1
[20700:0530/115338.695:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:38 AM] IPC#vscode-workbenchLoaded
[20700:0530/115338.992:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115339.314:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[main 11:53:39 AM] IPC#vscode:broadcast vscode:changeColorTheme {"id":"vs-dark vscode-theme-defaults-themes-dark_plus-json","background":"#505050"}
[main 11:53:39 AM] windowsService#isFocused 1
[20700:0530/115341.222:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115341.718:INFO:CONSOLE(1305)] "%cTRACE", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1305)
[20700:0530/115343.396:INFO:CONSOLE(260)] "%c[Extension Host] %crejected promise not handled within 1 second %c(at Timeout._onTimeout (m:\Apps\Code\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:700:9))", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (260)
[20700:0530/115343.396:INFO:CONSOLE(1306)] "%c ERR", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js (1306)
[20700:0530/115346.225:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115351.226:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115353.419:INFO:CONSOLE(20)] "ApplicationInsights:Sender", source: M:\Apps\Code\Microsoft VS Code\resources\app\node_modules.asar\applicationinsights\Library\Logging.js (20)
[20700:0530/115356.230:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115401.233:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115406.236:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[main 11:54:06 AM] update#checkForUpdates, state = idle
[main 11:54:06 AM] update#setState checking for updates
[main 11:54:06 AM] RequestService#request https://vscode-update.azurewebsites.net/api/update/win32-x64/stable/3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9
[main 11:54:06 AM] Error: net::ERR_INTERNET_DISCONNECTED
[main 11:54:06 AM] update#setState idle
[20700:0530/115411.239:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115416.242:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115417.577:INFO:CONSOLE(79)] "Uncaught Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'

Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js (79)
[20700:0530/115421.245:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115421.679:INFO:CONSOLE(20)] "ApplicationInsights:Sender", source: M:\Apps\Code\Microsoft VS Code\resources\app\node_modules.asar\applicationinsights\Library\Logging.js (20)
[20700:0530/115426.248:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115431.251:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115436.256:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115441.259:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115446.262:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115451.265:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115456.268:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115501.271:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115506.273:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115511.275:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115516.278:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115521.280:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115526.283:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115531.286:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115536.288:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115541.290:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.
[20700:0530/115546.293:WARNING:dns_config_service_win.cc(661)] Failed to read DnsConfig.

I have added your code to a little script to run whole instances at once like so:

const logger = fs.createWriteStream('logger.log');
dirs.forEach(dir => {
exec('code . --verbose --disable-extensions', {cwd: dir} ,(err, stdOut, stderr) => {
logger.write(stdOut);
});
});

Because it's logging on first instance so I hope there will be no problem with logger output.
I hope to capture the error there with this logger.
Thanks.

[Tyriar]

Appears to be related to localization.

[dbaeumer]

@miladelecancy couple of questions:

• do you have a language pack installed. If so which one
• is this your correct user directory: C:\Users\m or is it truncated ?

[miladelecancy]

Hi @dbaeumer .
no i have no language pack installed. By the way i'm using 3 extension packs:

1. Angular language service 0.1.9.
2. Auto Import 1.5.3.
3. TSLint 1.029

C:\Users\m is my path and is not truncated.
It's a little bit strange. I'm not sure if it's worth to mention or not but this is no longer happened (about 12hrs) since I separate the angular instance terminal. I mean in one of my VSC instances I have a angular5 project. I have run 'ng serve' out of embedded VCS terminal in an external cmd prompt and since then this is not happening at least up to now.
actually now I don't use any of VCS's embedded terminals.

[dbaeumer]

I looked through our code and we create the C:\Users\m\AppData\Roaming\Code\clp directory in our main code (first thing executed) and if it fails we fall back to the English build in translation. @miladelecancy does that directory exist for you?

[miladelecancy]

OK good. no it's not existed.

[dbaeumer]

@sandy081 can you think of any code that runs in the shared process and tries to access the cache directory for language packs (e.g. AppData\Roaming\Code\clp).

[dbaeumer]

Regarding #50763 (comment): good to hear that it doesn't crash anymore. But executing something in an external terminal compared to an internal one is unrelated in terms of translation.

The internal terminal has some native code which I think could crash a VS Code instance.

[sandy081]

@dbaeumer It seems there is code that access clp cache directory here.

This is some language pack cache cleaner in shared process which you should be aware of I supposed.

[dbaeumer]

@sandy081 thanks a lot. That is even my code :-(

[dbaeumer]

To verify:

• delete the LP cache directory. Under Windows it is ${Home}\AppData\Roaming\Code\clp

• start code with --verbose from a terminal

• ensure that no exception like

Error: ENOENT: no such file or directory, scandir 'C:\Users\m\AppData\Roaming\Code\clp'", source: file:///M:/Apps/Code/Microsoft VS Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js (79)

is printed to the console.