Select to view content in your preferred language

ArcGIS Pro random freezing

10789
19
Jump to solution
05-06-2022 08:10 AM
necurri_VC_SSO
Occasional Contributor

I'm wondering if anyone out there has ever experienced all buttons and menus in ArcGIS Pro become unresponsive. It's not necessarily freezing in that I get no error, my CPU doesn't start going bonkers, I'm getting no indication that the machine or the program is hung on anything, but none of the menus or buttons respond to clicking. The only thing I can do is click the X button in Windows to close the program and save it when it prompts me. Or I can minimize or resize the program Window, which doesn't help much... I'm not seeing any pattern to it - no particular function or action seems to trigger it. 

Tags (1)
19 Replies
necurri_VC_SSO
Occasional Contributor

Just had a full on crash when editing so I'm trying it now.

0 Kudos
wayfaringrob
Honored Contributor

My coworker and I have the exact thing happen pretty frequently - sometimes a right click on something in the TOC will fix it, but usually not. I tried opening a tech support case but since it's intermittent/not reproducible and their steps didn't do anything to assuage the issue, they weren't able to do anything. One thing they suggested was to disable WebRoot, which I tried, and still had the issue. Keyboard shortcuts usually work, though, so you can press Alt+F4 to close and use the spacebar to select 'save' when prompted. And then reopening the program should work fine. Annoying, but a pretty quick workaround.

Y_Chau
by
Frequent Contributor

For me the save button is also grayed. Only option is to kill the app from task manager. This happens quite frequently. It consumes 60% CPU and 50% RAM with very ordinary amount of data. Our customers are reluctant to move to Pro because of this behavior.

0 Kudos
Robert_LeClair
Esri Notable Contributor

There is an ArcGIS Pro Diagnostic Monitor you can use to access status information, logs and events to diagnose application problems such as resource overconsumption that you're currently experiencing.  You can learn more about it here - Diagnostic Monitor—ArcGIS Pro | Documentation

0 Kudos
Y_Chau
by
Frequent Contributor

For me the problem was solved by a clean uninstall. I followed this Esri Australia Blog

Esri should build a tool to do this. Trimble used to have a cleanup tool for Pathfinder Office. It would remove all the folders and registry values.

0 Kudos
Bud
by
Esteemed Contributor

@KoryKramer might find wayfaringrob's workarounds interesting.

…sometimes a right click on something in the TOC will fix it, but usually not…Keyboard shortcuts usually work, though, so you can press Alt+F4 to close and use the spacebar to select 'save' when prompted. And then reopening the program should work fine. Annoying, but a pretty quick workaround.

0 Kudos
wayfaringrob
Honored Contributor

The issue persists in Pro 3.0. Map navigation seemed to be working (the thing I did right before it broke was zoom to a group layer, and it worked again when everything else was locked up). It responded to right clicks in various locations, but not left clicks. Right click > Symbology seemed to get it to snap out of it.

0 Kudos
wayfaringrob
Honored Contributor

Happened again today, all I did was R click>open a map from the catalog view, and then I couldn't click anything.

0 Kudos
Sheller
New Contributor

I am so frustrated with AGP freezing that I decided to see if others are having the same issues.

I upped my RAM, copied all files locally, and it still locks up randomly and I have to envoke the task manager to close it up and lose all the work that hadn't yet been saved. I was taking 2 steps forward and 1 step back every hour or so and I had enough and just started doing the same work with Arcmap 10.8.1. 

It has not crashed once since I did this. My production has increased and I think I have to click 40% fewer times to do the same job. Why can't they get this right? I have been trying to move to AGP for 10 years and every time I do I end up back with Arcmap. Not because it is easier and more familiar, but it actually works much better.

necurri_VC_SSO
Occasional Contributor

In my case, it turned out my computer was sick. After the computer was reformatted and everything reinstalled, I've not had the problem again. 

0 Kudos