It is truely weird, as I am not having the problem now. I can't isolate what is running, not running on my machine when it is happening, though it seems as the the "programmer stress detector" seems to be the factor, as it seems to happen most late at night when I have a critical demo the next day. Really baffling me, but I am on site at my customer and it seems ok at the moment. I can't relate number of vi's open, or complexity (some have a moderate to high number of controls/indicators, but they aren't always even in memory, other than how ever much is loaded when the project itself is loaded (that is an interesting question, how much is loaded when a project is loaded, but no calling vi's for a particular vi are?)
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion