I frequently have several instances of Pro open at once, e.g. when I know some geoprocessing is going to take all day.
Sometimes, I end up having to kill one of those instances because what should have taken 30 seconds has been going for an hour and it's time to cut and run.
When this happens here are my options:
I prefer Option 3.
The issue, however, is that there isn't any way to tell which APRX you're nuking.
While waiting for the geoprocessing tool or the map drawing or whatever, Pro is considered "responsive", so we don't even get a warning about that.
You can also maybe switch to the instance? Idk about that though, I have inconsistent results.
The easiest way would to just have the APRX name listed in Task Manager. That would make figuring out which APRX is the problem a lot easier. Please add this in.
For context: v 3.1.3
I've seen it work maybe twice in my life.
This is what I got this morning:
(No, my being signed in or out of a portal does not make a difference. The first pic I was signed in, the second I was not.
That's right,
Not always there in any version of Pro.
I have a standalone version of the current versions of Pro, no portal, just local everything, perhaps that is the difference
Me too
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.