## Bug Description As described in https://scilab.discourse.group/t/great-visual-debuging-and-variables-inspection/799?u=davcheze : after a few seconds or tens of seconds during which everything is running as expected in VS code environnemnt, some features are abruptly stopped and a visual error notification is raised by VScode. The stopped features are at least the integrated documentation hints, the function outline and ctrl+click on Scilab function. ## Steps to reproduce VScode with Scilab (both WIN10-64 installations, in local user installation directory \AppData\Local\scilab-2025.0.0 ) VScode settings and debug configuration as explained in getting started, with no trouble during a while (5 s), when trying to write/edit the current .sci file, after a while I got error message in the output tab Scilab Language Server (when moving the mouse over any scilab function ( mgetl, csvTextScan,…) or argument autocompletion of function, ). While was showing nicely the documentation as hint during a few seconds, it issues the error message in VScode Output tab: ## Error log ``` [Error - 5:27:59 PM] Stopping server failed Message: Cannot call write after a stream was destroyed Code: -32099 [Error - 5:27:59 PM] Stopping server failed Message: Cannot call write after a stream was destroyed Code: -32099 [Error - 5:27:59 PM] Server process exited with code 3221226505. ``` After that, I can’t recover the environment features automatic function argument completion or documentation about function under the mouse pointer, until I restart VScode or start to write a new file. Also the function list in current file is not anymore available in OUTLINE view and the CTRL+click on scilab function neither works when the scilab language server issues.   As mentionned in discourse thread: installation of Scilab 2025.0.0 with local admin privileges didn't solved the issue on office computer when running the VS code still installed in user local directory \AppData\Local\Programs\Microsoft VS Code . On my personnal computer, i installed from user local admin session both Scilab 2025 and VS Code and everything is running there like a charm as described in documentation, without any issue even after several minutes. I hope it can help to trigger this tricky issue, I'm blocked on this at work. Thanks, David