Memory usage during sonar analyzing (Azure Devops/C#)

I am still experiencing a lot of memory usage of sonar scanner two times more since 11th of October, should that have been addressed? I was used to use 4Gb and now I am up to 10Gb of memory.

Help appreciated!

Hey there.

On October 11th we deployed a pretty significant update to our security analyzer which included improvements for C# analysis. This might be the cause of the increased memory usage (and it might not be entirely avoidable). Still, I’ll flag this for attention from the right team.

Make sure you have your analysis logs ready to share with them!

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

Hey Colin,

I have created some log files… Do I need to redact them and share them?
Or which parts should I share or investigate?

Hey Quint,

thanks for reporting this.

As Colin stated, it was expected that more memory would be used.
In this particular case, the increment seems rather large.
We would like to take a closer look at your case.

Please share any information that helps us to reproduce the scenario.
This may include your (redacted) logs as well as any shareable information about the project you analyzed (e.g., a repository link if it is an open-source project) and how you analyzed it (e.g., which scanner was used).
It would be a plus, if you could also share logs from before October 11th.
If you are not comfortable with sharing logs or any other information here, feel free to share them with me privately.

Let us stay in touch!


1 Like

Sure… I tried to revert back to old memory usage with out any luck… Now using 8G instead of 4G :frowning:

How can I share those logs privately?