-
Notifications
You must be signed in to change notification settings - Fork 440
Open
Labels
analyzer 📈Related to the analyze commands (analysis driver)Related to the analyze commands (analysis driver)enhancement 🌟performance 🏃
Milestone
Description
Describe the bug
When analyzing a project with ten thousands of source files the analyzis consumes all the memory
CodeChecker version
6.22.1
To Reproduce
- Check out the Linux kernel
- Create a .config file by executing e.g. 'make menuconfig', then press 'Save' and 'Exit'
- Build the kernel while logging it, e.g.: 'CodeChecker log -o linux.json -b 'make -j4'
- Analyze the code: 'CodeChecker analyze -o analyzis linux.json'
Expected behaviour
Analysis should have started properly. However, it does not happen but all the memory of the computer is consumed by CodeChecker itself (actually the third CodeChecker thread), without starting any analyzer.
Desktop (please complete the following information)
- OS: Ubuntu Linux
- Browser: n/a
- Version: Distribution version 23.04, kernel version 6.2.0
Additional context
There are about 60000 files to analyze. When I split the log into 4 equal parts, the analysis starts but my 8Gb of memory is almost consumed by CodeChecker, not the analyzer engines.
Metadata
Metadata
Assignees
Labels
analyzer 📈Related to the analyze commands (analysis driver)Related to the analyze commands (analysis driver)enhancement 🌟performance 🏃