Can you let me know why does we have errors in diagnostic monitor, steps to create are as follows:
--> Start ArcGIS Pro with /enablediagnostics
--> Open project without template
--> Add map
and once the map is loaded then we see the errors in diagnostics monitor :
Missing class or assembly name: esri_mapping_edgeSnappingButton
Missing class or assembly name: esri_mapping_intersectionSnappingButton
Missing class or assembly name: esri_mapping_tangentSnappingButton
Missing class or assembly name: esri_mapping_snapChipToggleButton
etc [Attached screenshot]
I also have this error message and would like to know what it means. I have a Brand-new laptop and I'm trying to diagnose why it takes so long to draw my aerial now compared to my old laptop.
I have this also - running ArcGIS Pro 3.3.2
I would also like to know.
Hello,
My Pro 3.4 has been crashing all the time lately and I noticed that the Diagnostic tool says its missing esri_mapping_snapChipToggleButton.
Has anyone figured this out yet?
Help appreciated,
Amy Rose
Dallas, TX
Are you using a custom add-in? If so, I would try removing it this time. Does ArcGIS Pro still crash?
Hello,
No, no custom add ins but my computer in general has started to have issues. I may have to have it wiped clean and re-install everything. 😞
I and others in my organization are getting the same esri_mapping_{}SnappingButton errors in Diagnostic Monitor in Pro 3.3 in multiple APRXs.
I removed my Add-Ins and it made no change.
Task Rate and Waiting are lit yellow, with 3 Foreground Threads, but the map and layout elements won't render. I have to force quit Pro currently.
Paging @KoryKramer
Update: I ran "Can I run this" for my version of ArcGIS Pro and saw that I did not have the required 20 GB of free disk space (not RAM or GPU). I was currently at 185 out of the 200 GB assigned to my virtual machine. I cleaned out the Download and TEMP folders, which got it down to 170 GB (!). I'm not sure what all is getting saved by Pro in those TEMP folders, but clearing the cache in Pro does not clean them out. Once I deleted all the data in the TEMP folder, I was able to render the layout, save and move on. We'll see if the issue comes back if the storage space creeps back up, or if it's something else being created in TEMP (C:\Users\{username}\AppData\Local\Temp).