Every morning when I start up Pro, I get the blue Windows wait cursor for about 10 minutes. Doesn't matter if I open an existing aprx or create a new one. I can pan the map and navigate panels but I can't do anything other than that. Force quitting it and starting it again doesn't resolve it, it just needs 10 minutes to wake up.
If I leave Pro unused for about an hour the same thing happens when I try to resume use.
I've reinstalled it, cleared cache, all the usual stuff so far nothing has helped.
This often costs me up to an hour of work per day. I'm guessing my boss probably wouldn't like to hear that, that adds up pretty quickly.
Solved! Go to Solution.
Here's a good blog article regarding ArcPro performance tips:
https://www.esri.com/arcgis-blog/products/3d-gis/3d-gis/troubleshooting-performance-issues-in-arcgis...
132 08:11:11:422 133120 15 0 133105 ArcGIS.Desktop.Editing.TopologyService.GetGeodbTopoInformation
131 08:08:25:213 299324 0 0 299324 ArcGIS.Desktop.Mapping.MappingModule.InternalFillFeatureCache
130 08:08:22:511 302023 16 0 302007 ArcGIS.Desktop.Editing.BulkServiceCaller`2.Request+
129 08:08:22:422 302088 0 0 302088 ArcGIS.Desktop.Editing.QueryService.SetSketchPlaneIDToNegative
128 08:08:22:360 302150 0 0 302150 ArcGIS.Desktop.Editing.QueryService.QueryMemberPropertyAsync
127 08:08:22:322 302188 302187 0 1 ArcGIS.Desktop.Internal.Mapping.ViewerPaneViewModel.HasArcGISClipboardText
So the clipboard?
Thanks everyone for your help, it actually is the clipboard.
I'm working remotely and accessing Pro through Citrix on a Mac. In the Remote Desktop Connection settings, there is a setting to share the clipboard. If I uncheck this, Pro no longer hangs on me (although the screen redraws a whole lot more on launch for some reason).
I don't know if it's a Citrix client or server issue, an ESRI issue, or something with my particular setup. It does complicate things a little bit that I can't share the clipboard but I'll get by.
If anyone happens to know anything about this issue please let me know.
I suggest creating a new local user. Use the Runs As option and start Pro as the new user. The first time may take a while because its build the profile for that user. After that it should start faster. You can also log in the system with the new account and start Pro. If you cannot reproduce the issue, it's likely something stored in your profile. If that is the case, there are certain things in your profile or registry you can edit. See if you can reproduce the issue with a new user first.
Is this in response to my original post or the latest? I've tracked down the issue as a RDC clipboard issue and mostly resolved it. I should probably mark it as solved.
Thanks