-
-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fsautocomplete is not killed when extension is closed #1703
Comments
This could be related to an issue of Note I tried updating to
Full of logs``` Starting target 'RunScript' /repo/vendor/ionide-vscode-fsharp> "dotnet" fable ./src/Ionide.FSharp.fsproj -s --outDir ./out --run webpack --mode=production (In: false, Out: false, Err: false) Fable: F# to JS compiler 3.7.8 Stop Russian aggression against Ukraine!Parsing src/Ionide.FSharp.fsproj... Started Fable compilation... ./paket-files/ionide/ionide-vscode-helpers/src/Helpers.fs(86,24): (86,42) warning FSHARP: This construct is deprecated. Use { (code 44) ERROR in ./node_modules/vscode-languageclient/lib/node/main.js 267:50
| if (options.execArgv) { Build Time ReportTarget Duration Clean 00:00:00.0094844
|
I think it is realted to that issue @vain0x. The FSAC LSP implementation recently took a fix around this that we haven't released yet, but I agree that updateing to the v8 version of the language client will be the correct fix. That'll be a multi-step operation, though, as the F# bindings need to be updated first. |
This will be fixed by #1713 |
I am no longer experiencing this issue with Ionide v6.0.5. |
Describe the bug
Closing and relaunching VS Code or executing the Reload Window command creates a new
fsautocomplete
process but does not kill existing ones. Over time, many processes are created and consume lots of memory.Steps to reproduce
Just close and reopen VS Code a few times or use the Reload Window command. Observe the instances of
fsautocomplete
in a process viewer.Expected behavior
All processes spawned by the extension close with it. Only one instance of
fsautocomplete
is present at a time.Machine info
Additional context
I captured logs of the active
fsautocomplete
processes using a small shell script,watch-ionide
. Observing the changes in PIDs from several runs, I noticed that when restarting VS Code completely has a tendency to eventually stabilize to a fixed number of running processes while reloading will keep increasing the number of processes without bound.reload.log
restart.log
Here are the logs from the extension window for the same two trials.
extension-reload.log
extension-restart.log
Not sure if it matters, but I'll mention that I launch VS code with
--extensions-dir="$XDG_DATA_HOME/vscode/extensions"
.The text was updated successfully, but these errors were encountered: