Closed Chovin closed 3 years ago
Were you by chance able to capture an error in your dev tools console?
I didn’t see any error other than extension host crashing and it giving me a list if extensions that were installed. Would you happen to know how to get a more detailed error?
I have encounter the same error. I used VS Code Extension Bisect to determine this extension was the cause. I thought it could have been because I am using vscode sync onto a this rebuilt machine and it logged me out, but even after logging in I get the error. I am using a Mac Air 2015 with Big Sur 11.1
VSCode Version: 1.52.1 Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523 Date: 2020-12-16T16:30:02.420Z (1 mo ago) Electron: 9.3.5 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Darwin x64 20.2.0
Not sure if the following is relevant but here you go.
I also have an issue with this extension. Works fine most of the time, but when I install Ionide-fsharp for F# language support, this extension causes the extension host to crash.
[LineLens] Config Changed event
[LineLens] Installing
[LineLens] Installed
[PipelineHints] Config Changed event
[PipelineHints] Installing
[PipelineHints] Installed
[GitIgnore] gitignore path: c:\Users\jh\code\F#\test\.gitignore
[GitIgnore] Error accessing gitignore file [Error: ENOENT: no such file or directory, open
'c:\Users\jh\code\F#\test\.gitignore'
at Object.openSync (fs.js:466:3)
at Object.func [as openSync] (electron/js2c/asar_bundle.js:5:1812)
at Object.readFileSync (fs.js:368:35)
at Object.e.readFileSync (electron/js2c/asar_bundle.js:5:8583)
at Ru (c:\Users\jh\.vscode\extensions\ionide.ionide-fsharp-5.3.2\fsharp.js:2:490245)
at c:\Users\jh\.vscode\extensions\ionide.ionide-fsharp-5.3.2\fsharp.js:2:490460
at Object.then (c:\Users\jh\.vscode\extensions\ionide.ionide-fsharp-5.3.2\fsharp.js:1:54273)] {
errno: -4058,
syscall: 'open',
code: 'ENOENT',
path: 'c:\\Users\\jh\\code\\F#\\test\\.gitignore'
}
Can confirm this issue also occurs in vscode 1.54.1 macos.
Thanks for the update and the error report. That's helpful
We have confirmed that the latest versions 2.1.14 and 2.1.16 have the fix for this issue, thank you.
Describe the bug
ISSUE TYPE
Steps to reproduce
Restart Extension Host
)Expected behavior
ACTUAL RESULTS
Screenshots
Desktop (please complete the following information):
Additional context