#How do i force stop the language server
1 messages · Page 1 of 1 (latest)
i did. it didn't solve my issue though. i hope it prevents it instead
Yeah I believe it will only affect language servers launched after the flag is toggled (you may need to reload the window for it to take effect)
It happened again, this time with agressive shutdown already on. it didn't prevent it
and now even after a restart it still affects it
I just wish there was a way to manually close the program
that would save me the hassle of shutting down my entire pc
and then starting it again
Sorry what do you mean by force stop it from running? Is it hanging around even after you close VSCode?
yep. it is. only when i shut off the power to my desktop (without a battery) it finally closes and resets itself
Any other technique doesn't work to stop it
TLDR; i had this setting on and it still happened
it keeps running even after a force close of vscode
It just keeps trying to process the input that made it crash in the first place even after restarting my pc multiple times
i can't type inside or select the input window
So any option to acutally be able to close the codeium process would be amazing
Okay so i did some further epxerimenting
i was able to kill the langauge processs
which just displayed this error for me:
Error getting user status: [unavailable] connect ECONNREFUSED 127.0.0.1:33765
if i then log out i am able to type again inside the window. but due to me being logged out i cannot actually use the service
So that didn't help. upon re-logging in i get the same error again
and here's the crazy part
once i restart vscode. it just bugs out all over again and i am back to being unable to type anything inside the codeium window
I updated my vscode, did multiple computer restarts, crashed codeium multiple times, logged out and back in as much as possible and yet it still hasn't shut down itself.
i just hate there's no way to reset it somehow
After closing VSCode can you show where you see the language server process running?
Looping in @fallen turret
It might not have been a running instance issue
I completely fixed it by deleting my .codeium folder
and letting it recreate it
I found a reproducible input
it is extremely long. so if i could find a way to access codium from the console i could write a python program to check every possible shorter version of it.
So there's a specific input you provided that broke chat for you?