#is that how it supposed to work i closed
1 messages · Page 1 of 1 (latest)
nope, i don't need it
I wonder if this is an issue for windows - will come back to you on this. Do language servers ever get cleaned up properly?
you mean if that problem was noticed earlier? if so, i really don't know, i noticed it accidentally
how many language SUBprocesses should run under vs code proccess?
i see 2
even bisect says it's codeium problem
when i reload vs code (not restart, reload via bisect), new lang server subproccess appears
so during bisect there were 5-6 language server subproccesses :D
Yes, two is correct
so there’s no fix at the moment?
We’re reproducinginternally
i found the culprit
it’s Search
when i turn it off, language server terminates correctly