DUnit2 + FastMM4 bug
Brought to you by:
pvspain
I'm using OmniThread Library, FastMM4 and DUnit2 and the combination is not a good one. In this thread on the OTL forums there's sample code and discussion of the problem: http://otl.17slon.com/forum/index.php/topic,144.0.html
Basically, Dunit2 reports memory leaks on most tests but FastMM4 does not report those leaks at shutdown. Running the demo app in the debugger is fine, outside the debugger there's an access violation and no tests run.