Jump to:

A user reported what looks like a memory leak in NAADSM 3.2. In a test run on Windows, the scenario consumed 76 MB of RAM at the start of the first iteration. By the end of the first iteration, 137 MB of RAM were used. At the start of iteration 2, 137 MB of RAM were still in use by the application. I would have expected a considerable drop in memory usage when the second iteration started.

I have run the scenario with EurekaLog (the Delphi/Windows equivalent of Electric Fence) to check for memory leaks in the GUI. None were found.