Please provide
- Operating system: Windows 11 Enterprise 25H2
- SonarQube for IntelliJ plugin version: 11.14.0.84231
- IntelliJ version: 2025.3.3
- Programming language you’re coding in: Java
- Is connected mode used: yes, SonarQube Cloud (Issue also occurs without connection)
And a thorough description of the problem / question:
My setup is as follows:
- WSL version 2.6.3.0, Ubuntu
- My project is living in Ubuntu 24.04.3
- IntelliJ is running on the Windows host
- I opened the project with the normal Windows file browser of IntelliJ’s “Open project”, not any form of “Remote Development”
When I run the analysis on any file, even a completely empty class (public class Dummy {}) in my project, it takes around 20 to 30 seconds for each file, and hence, also when fixing issues, it around that time for the findings to update.
I managed to reproduce the issue in a brand new project as well, created with IntelliJ’s project creation tool. I will attach a zip of that as well (sonarqube-demo.zip (103.8 KB)). That’s when I realized that it’s probably related to the amount of dependencies the project has, as in the brand new project, a scan took less than a second. It remained fast, even when I copied over the whole src directory from my actual project. Obviously, most dependencies were missing, so I wasn’t sure if that’s something to do with it. Then I added the gradle.build file as well, and the behaviour was the same as in my original project, and it remained slow when I reverted the code to the minimal example, but left the dependencies in.
I attach the flight recordings of both setups, one with several dependencies, and one without. In both cases I simply ran “Analyze Current File” in Main.java
Another note: When I open IntelliJ in WSL via WSLg, the scan performance is as if I scan a project living on host with the host IntelliJ, so it seems to be specifically a WSL-files/host-IntelliJ problem.
many_dependencies.zip (54.5 KB)
no_dependencies.zip (48.0 KB)
