Title: VS Code Extensions Terminate When SonarLint Runs Async Tasks on Multiple PDF Files
Operating system:Windows 11 / Ubuntu 24.04 LTS
Sonarqube for VS Code plugin version:v4.9.1 (latest at time of testing)
Programming language:Python (Async I/O tasks involving multiple PDF files)
Is connected mode used:No – running in standalone mode (not connected to SonarQube or SonarCloud)
Description of the problem
While executing asynchronous Python code that processes multiple PDF files in parallel, the SonarLint extension for VS Code terminates unexpectedly.
When this occurs, other VS Code extensions also stop or fail to launch properly, indicating that the VS Code extension host may be restarting or crashing.
The issue consistently appears when:
•Multiple async file I/O tasks run simultaneously.
•SonarLint’s background analysis triggers during or after file processing.
•The workspace has several active extensions (such as Python, Jupyter, or formatters).
It seems that SonarLint’s analysis process or resource handling during async execution causes instability within the VS Code extension host.
Expected behavior: SonarLint should run stable even during high async workloads, without affecting other active extensions or causing the extension host to terminate.