Clover Results Collector causes OOM on agents for large Clover XML report files

Automatic/manual Clover integration mail fail.

Problem:
Parsing Clover's XML report file consumes ~7 * file size of the heap memory. In case of large projects and thus also large XML report files, it may cause that a build agent will fail with an "out of memory" or a "GC overhead limit exceeded" error.

Workaround:

Don't generate large XML Clover coverage reports. Prepare a custom configuration for an XML report to make it smaller.

In case of Ant:

• if you're using automatic Clover integration, then the reporting target is named "clover.report" (see clover.jar/clover.xml file); define such target in your build.xml file to override default settings
• if you're using manual Clover integration, then find your target responsible for report generation
• disable generation of source line information for XML report in order to reduce file size

Example:

<target name="clover.report">
        <clover-report>
            <current outfile="target/site/clover">
                <format type="html"/>
            </current>
            <current outfile="target/site/clover/clover.xml">
                <format type="xml" srcLevel="false"/> <!-- USE srcLevel=false" -->
            </current>
        </clover-report>
    </target>

In case of Maven:

• use the reportDescriptor to customize the report - see https://docs.atlassian.com/maven-clover2-plugin/latest/clover-mojo.html#reportDescriptor