It happened again - I buried hours into a search for a memory leak somewhere in TestStand.
This time a rogue loop never left MainSequence and caused Locals.ResultList to grow unlimited (not leaving Main was not so obvious in my setup as it may sound - but that's not the point I'm after here).
Until I looked at exactly the right place I had no idea what was eating up my memory. All the profiler tools I know of just gave me the information that something in the TS-memory grows out of control but there was nothing that helped me to narrow down my search. Actually - the first indication that something was wrong was an ever growing number of handles in the Windows Taskmanager, nothing inside TestStand.
I'm missing a way to get information about:
- all variables (within current threads/executions/engine) and their size
- all Queues, Notifications, Semaphores
I'm aware that there are security considerations involved but I could imagine that data to appear in Execution Profiler.
This could be an entry in Idea Exchange but maybe something is already something else out there. (?)