Hi Rajaganesh,
With each plugin upgrade, there are often new rules being added, specially now on the security side, which may require more memory. However, we need to make sure this is either a potential memory leak on our side or an expected issue due to memory really lacking on your system.
Could you please share here:
- The full log where the error is being shown. If this happens on the server side, then this should be the ce.log file.
- The sonar.ce.javaOpts, sonar.web.javaOpts and sonar.search.javaOpts settings you were initially using.
- The size in lines of code of the project you are scanning.
- Is your server machine exclusively dedicated to SonarQube, or is it running other potentially memory-hungry processes (e.g. database etc). Are you launching the scan from a separate machine?
Regards,
Daniel