"The Typescript language service died" running on a network drive through Linux smb

[ole1986]

• VSCode Version: 0.10.11
• OS Version: Windows 10

Steps to Reproduce:

(does not need a step or maybe when opening a JS file)

Receiving "Warn: The Typescript language service died unexpectedly 5 time in the last 5 Minutes. Please consider to open a bug report." ... and it does not stop showing me the popup.

[egamma]

@ole1986 can you please check whether this the same setup as in this issue: #3860?

[ole1986]

strange thing is after I fully rebooted the system it is gone (until now)

[egamma]

Is your workspace very large and has lots of .js files?

[ole1986]

Actually not! I just added one new js file via the "New File" button...and it was empty.. then the warning appeared. After adding some text it still pops up. So I restarted the whole machine.. Than it was gone.

[egamma]

Is the workspace on a sharepoint/webdav mounted volume as in #3860?

[ole1986]

No, but on a network drive through Linux smb

[egamma]

If the same setup works on a local folder, then this looks like the node issue described here #3860 (comment)

[waderyan]

@ole1986 are you still seeing a similar issue today? Closing this assuming its fixed in later versions. If the problem is persisting then please ping me and I'll reopen.

[jpalo]

I'm still getting this on SharePoint WebDAV on 1.8.1. Strange thing is that server.log is pretty much empty, and there is new ti* log file being generated on each time error message reappears at the top in VSCode (once every few seconds).

1. Open SP folder in VSCode (site collection master pages library folder, such as https://sp.com/m/kd/_catalogs/masterpage/portal)
2. Open another SP folder in VSCode (root site collection master pages library folder, such as https://sp.com/_catalogs/masterpage/portal)
   --> Error occurs only on the second VSCode instance, order of 1/2 doesn't matter it only occurs on root site collection (step 2)

Difference between the folder is that the one that doesn't cause the issue has only 10 .aspx files, while the one causing the error has 51 items at the root, of which 8 are folders and rest are mainly .js files + few .aspx files. Summing up all files at the root and in subfolders, there are 1281 files (as it is DEV installation with lots of bower files). If I remove bower files, so total file count is 194 files, issue still occurs, also with 115 files. Conclusion, it is not about the file out per se.

Wild guess is that it might be related to the ghost files I can see even though I've deleted them via Windows Explorer - they are still shown in Windows Explorer, but aren't really there?!

Log