Slow Performance of TestDesigner gets worse each day of editing NavMaps.
CountDown will start consuming more and more RAM resources as you run TestDesigner day after day without restarting TestDesigner. All the screens and component information is saved in RAM as the Navigation Maps are edited and this RAM is not released until user saves and exits TestDesigner. This is working as designed.
- The recommended usage is to save, exit, and restart TestDesigner at minimum of once a day.
- Increasing RAM on the computer is also very helpful with TestDesigner performance.