Thank you @duncanp and @Kirill_Knize for your responses.
@duncanp I’m using vscode-insider. Yes each instance only listens on one port, but opens around 65 ports, which appear to be back to itself. I’m more concerned about the 65 ports that are consuming ports I use, e.g. 3306 in the above screenshot is the default MySQL port. Also I have more than one window of vscode open and so have more than one instance of the extension open, so the number of ports being consume quickly multiplies.
@Kirill_Knize The above image is from Process Explorer looking just at the process
java -jar sonarlint-ls.jar ... and so they are a reflection of all the ports being consumed by that process alone both in listening and any internal and external network connections. I see the same number of ports being consumed for each and every instance of this process all the time (first load of vscode, reload after update, etc.). These connections are permanently open, rather than changing over time.
Would you be able to open a tool that tracks network connections to check this? netstat will show them as java.exe, so the following Powershell will show you
netstat -abn | select-string -Context 2 java.exe. Process Explorer makes it much more obvious that the above process is the cause and is powerful in many other ways, so I would recommend taking a look at it.
I’m now using SonarLint 3.1.0 with the same result.