When I use 1.88, then cppcheck takes something around 500-1000MB, but when I use 1.90, then in some moment Cppcheck will take more and more memory and at the end it will crash system(I have on computer 24GB Ram)
Steps to reproduce:
1. Download krita source code git clone https://invent.kde.org/kde/krita.git;cd krita
2. Check it with Cppcheck with this command cppcheck -q -j8 --enable=all --suppress=missingIncludeSystem --suppress=variableScope --suppress=ConfigurationNotChecked --suppress=unusedFunction --force --xml --xml-version=2 . 2>&1 | tee cppcheckTEMP.xml
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes there is too much recursion during the analysis. We try to detect such problems with daca@home. krita is checked there too (in version 4.2.9 which is the latest tag). It did not seem to cause problems with the options used there: http://cppcheck1.osuosl.org:8000/krita
That does not mean that there is nothing wrong with Cppcheck. But it seems to depend on something.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I use 1.88, then cppcheck takes something around 500-1000MB, but when I use 1.90, then in some moment Cppcheck will take more and more memory and at the end it will crash system(I have on computer 24GB Ram)
Steps to reproduce:
1. Download krita source code
git clone https://invent.kde.org/kde/krita.git;cd krita
2. Check it with Cppcheck with this command
cppcheck -q -j8 --enable=all --suppress=missingIncludeSystem --suppress=variableScope --suppress=ConfigurationNotChecked --suppress=unusedFunction --force --xml --xml-version=2 . 2>&1 | tee cppcheckTEMP.xml
Sometimes there is too much recursion during the analysis. We try to detect such problems with daca@home. krita is checked there too (in version 4.2.9 which is the latest tag). It did not seem to cause problems with the options used there: http://cppcheck1.osuosl.org:8000/krita
That does not mean that there is nothing wrong with Cppcheck. But it seems to depend on something.