I have created an MCVE of a seeming bug in FastMM4/Dunit's memory leak detection.
I have created an MCVE of a seeming bug in FastMM4/Dunit's memory leak detection.
The test project contains a single testcase that deliberately leaks memory, which should be detected by FastMM4 and should cause the test to be failed given the options in force, but does not.
The problem can be "fixed" by various quite unrelated changes. I'm rather puzzled as to what might be going on and I'd appreciate someone else having a look (and/or confirming they can also see this bug/issue) The project is here:
https://github.com/ByteJuggler/FastMM4_LeakNotDetectedDemo
Thanks in advance.
The test project contains a single testcase that deliberately leaks memory, which should be detected by FastMM4 and should cause the test to be failed given the options in force, but does not.
The problem can be "fixed" by various quite unrelated changes. I'm rather puzzled as to what might be going on and I'd appreciate someone else having a look (and/or confirming they can also see this bug/issue) The project is here:
https://github.com/ByteJuggler/FastMM4_LeakNotDetectedDemo
Thanks in advance.
/sub
ReplyDeleteSo I'm assuming the upvotes mean you also see the behaviour but don't know what's wrong? :)
ReplyDelete