Open TilKenneth opened 7 months ago
oleg-shilo
commented
7 months ago Can you please check what was that dotnet instance running?
Is it "C:\Program Files\dotnet\dotnet.exe" exec "C:\Program Files\dotnet\sdk\8.0.100\Roslyn\bincore\VBCSCompiler.dll" "-pipename:JuwiWgO5bKHRRSyz6+a4qbQahJpQMqADd3KXUnZ5CGE"
or
dotnet C:\Users\oleg\AppData\Roaming\Code\User\cs-script.user\dotnet\syntaxer\syntaxer.dll
TilKenneth
commented
7 months ago REM Offending Process Path
"C:\Program Files\dotnet\dotnet.exe"
REM CmdLine
"dotnet %USERPROFILE%\AppData\Roaming\Code\User\cs-script.user\dotnet\syntaxer\syntaxer.dll -port:18003 -listen -client:25096 -timeout:60000 -cscs_path:%USERPROFILE%\AppData\Roaming\Code\User\cs-script.user\dotnet\cscs.dll"
REM CWD: %USERPROFILE%\AppData\Local\Programs\Microsoft VS Code\REM Process Path
"C:\Program Files\dotnet\dotnet.exe"
REM CmdLine
"C:\Program Files\dotnet\dotnet.exe" exec "C:\Program Files\dotnet\sdk\8.0.100\Roslyn\bincore\VBCSCompiler.dll" "-pipename:woio4wp_Ft0hUxCL0ccp10qgrtoa0OV_xaVlAJ1gHZs"
REM cwd=C:\Program Files\dotnet\sdk\8.0.100\Roslyn\bincore\>dotnet %USERPROFILE%\AppData\Roaming\Code\User\cs-script.user\dotnet\syntaxer\syntaxer.dll
CS-Syntaxer v3.1.1.0
Syntax provider for C# scripts (cs-script).
Copyright (C) 2022 Oleg Shilo (github.com/oleg-shilo/syntaxer.core)
Path: %USERPROFILE%\AppData\Roaming\Code\User\cs-script.user\dotnet\syntaxer\syntaxer.dllVBCSCompiler.dll is SDK, it's not use dby CS-Script. It's something else that starts it.
And, syntaxer.dll is a part of CS-Script extension. It's used for the intellisense. If it misbehaves you can kill it and the extension wil restart it with the correct args.
I will analyze syntaxer.dll utilization and see where the problems can be rtiggered. Most likely too many concurrent requests
TilKenneth
commented
7 months ago This happens only when I use %USERPROFILE%\.dotnet\tools\css.exe -vscode <file>.cs, opening VSCode independently it appears only syntax check (context menu) is performed, the Run/Debug options (top-right toolbar, context menu) has no apparent effect.
I tried using Selenium, css_nuget, it seems there are some CWD issues/NUGET/SystemProtection issues, but I want to resolve this issue before going further. I "solved" it (after Whitelisting cscs/css) and using -vs (2022 Community) and the NuGet package manager.
Question; I want to find any files from older releases, if I use the current release, will a system search for each filename also discover files from older releases? I think I am asking if any files from older releases is not present in the current release. I'll mention Notepad++, I think thats the only integration I tried, otherwise from ... well, thats why I ask.
oleg-shilo
commented
7 months ago Let's make it a little more clear. There are two very different scenarios that you mentioned here.
css -vs script.cs
In this case the script engine creates a simple VS project with the script being a comparable content.
Then it starts VS and loads the project into it. The rest is handled completely by VS and none of CS-Script family products is involved.css -vscode script.cs
In this case the script engine just opens VSCode and loads the file into it.
VSCode may or may not have folder/workspace already opened there.
The rest is handled completely by VSCode though if VSCode has CS-Script extension installed, it will start treating the cs file as a script.
dotnet syntaxer.dll ...), which is the engine of all Intellysence operations. It is an external process and all instances of VSCode will communicate with this service via socket on -port:18003.
Note, VSCode will block any extension that will try to work with the open document if it is the very first time you are opening it in the editor.
If your script ever stuck while being executed ("CS-Script is busy" error message) then you can always reset your session with "Ctrl+Shift+P":
I "solved" it (after Whitelisting cscs/css)
This happens a lot and not only to CS-Script :o(
Question; I want to find any files from older releases...
On the Releases page: https://github.com/oleg-shilo/cs-script/releases And .NET Framework edition, here: https://github.com/oleg-shilo/cs-script.net-framework/releases
So I am back again :-) I was going to to ignore this, and try with NppExec or try go to bed, but decided to try reproduce this nuisance, and I started by just clicking inside the opened file, and - it took less than 60 seconds. This writ however....
The building, running, debugging, intellisense, it all works, but with dotnet.exe forcing Windows and everything else, to be paged out of memory to a slow hdd pagefile. Not this picture, but it was at 10-12 GB (/16GB), it ate both my SSD pagefile and HDD pagefile, and I guess Windows just grew the HDD just enough to constantly alt+tab, delete (kill the task) in Taskmanger.
Environment for cmd.exe
dotnet.exe also has
Process tree;
wt.exe hosting cmd.exe:
D:\_TEMP\css_memory_exhaustion>css -vscode hello.cscmd.exe CurDir is
D:\_TEMP\css_memory_exhaustionCode.exe CurDir is%LocalAppData%\Programs\Microsoft VS Code\dotnet.exe CurDir is%LocalAppData%\Programs\Microsoft VS Code\Now I just did some sanity checks:
The other dotnet.exe (at about 100mb), CurDir at
%LocalAppData%\Programs\Microsoft VS Code: