Why is it when I have an image on my Windows machine where the UI is busy, that it makes any other image on my machine unresponsive (can't do anything in the UI)? I've seen this in development images and packaged images.
My current machine has 4 processors, so when one image is doing something in the UI process, it shows as pegging one CPU (25% total CPU usage according to the Task Manager or Process Explorer).
I've seen it in many versions of VAST over the years (and even *between* versions of VAST), so I assume other people have seen it. Perhaps the answer is common knowledge.