OutOfMemoryException about altcover HOT 5 CLOSED

The compression used in the visit file format means there can be a lot of visits per output byte if there are repetitive patterns.

As a work-around, if you are interested only in "did I visit this place?", rather than "how many times did I do so?", the --single command line option can significantly reduce the amount of data being processed.

from altcover.

Indeed, I tried this option already. Unfortunately I could not mention any difference.
The calls I do use are....

...for instrumentation:
$ALTCOV --single -i $WORKING_DIR -o $WORKING_DIR/instr/ -s xunit* -s ${TEST_ASM:0:-4} -s AWS*

...for running:
$ALTCOV Runner -x mono -c coverage/${TEST_ASM}.cort.xml -r=${WORKING_DIR}/instr/ -- $XUNIT ${WORKING_DIR}/instr/${TEST_ASM} -xml ./testresults/${TEST_ASM}.tests.xml

Note:
$ALTCOVER points to the altcover executable
$XUNIT points to the xUnit executable

from altcover.

I'll have to do some more investigation to see if I can find why --single seems to have no effect for you. In the mean time, pre-release build 656 contains a change that should mitigate the memory use for the intermediate processing, where the stack trace is indicating.

Could you give that a try?

from altcover.

I was some days occupied by other stuff, I will give it a try.

from altcover.

I tried the new release 659 and the exception didn't appear. Also the --single option seems to work.
Thanks for the quick fix!

from altcover.