Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
For my project (Gromacs) the memory usage of gcovr is extremely high when using the XML output (-x). It tops at about 1GB. This is with the version from https://software.sandia.gov/trac/fast/export/2745/gcovr/trunk/scripts/gcovr
(from ticket 3922)
Memory is an issue, but seeing as there is no test case demonstrating the problem and the reporter did not provide an address for correspondence, this is getting bumped down in priority.
The one thought that comes to mind is to move to stream-based XML generation instead of the current DOM-based approach for generating the XML. The DOM-based approach we are using now ends up with 2 full copies of the whole project's coverage information in memory at once (one for the data collection, and one for the DOM model).
I'm facing a similar issue with gcovr 3.2 using too much memory for XML output.
I've compared the three generators on my local machine (which has sufficient memory).
As you can see, runtime is generally not a problem but memory usage is.
Is there a special reason for using