When opening Ignition Designer, it uses the jp2launcher.exe application. Sometimes after closing Ignition Designer, the memory remains committed and isn’t released. (orphaned process).
Each jp2launcher app that has memory committed, uses about 1 gigabyte of memory; so if there are 6 jp2launcher.exe apps that haven’t released memory, that leaves 2GB left for all other processes.
At this point, if someone remotes into the desktop and opens Ignition Designer (another jp2launcher), or if an automatic process starts – that causes the maximum physical memory of 8GB to be exceeded, then RTM Ignition start to behave erratically.)
Is this a garbage collection issue?
What is your recommendation for this issue?
I’ve uploaded a picture of the task manager.