Why is Pro so terrible after all these years?

[_____]

I've been using ArcMap for as long as I can because it actually works, but I know it's being retired next year. I figured Pro would have a lot of improvements since I last tried to use it, but it's exactly as I remember... a buggy, unusable mess. All I'm doing is dragging a field over to the end of the attribute table and it crashes every single time (video attached).

Unbelievable... actually not at all, at this point I just expect it.

[BarryNorthey]

I have admin privileges on my home PC and use a personal use license so I can and do install upgrades as soon as they are available; no problem. This was not possible in my prior workplace that adopted the "managed desktop" software delivery approach in which every upgrade had to be "bundled" for delivery to desktops, whenever IT got in the mood. No one doing the bundling had any knowledge of GIS so I had to write out instructions for them back in the ArcMap days. It was also difficult bordering on impossible to get users to do routine maintenance on their bloating MXDs using the Document Defragmenter utility or to compact their fGDBs.

Our environment was designed for Microsoft Office. It was not designed to handle a complex package like ArcGIS that had frequent updates. Our network was not able to handle large spatial datasets but many datasets were force delivered that way causing processing delays and crashes. We even had to duke it out with IT to get decent (non standard) PCs for our higher end GIS analysts. 

In other words, there are many factors that can impact the GIS experience including the ability to keep current. A bug fix is only useful if you can install it. Software is often the culprit but I suspect that there are others in the mix depending on one's work environment. 

[ChrisUnderwood]

Hello @_____  , is that the current 3.4.3 version of ArcGIS Pro or a much earlier one ?

With a reproducible case like this, Esri's Support should be able to work out why this is happening for you. Certainly just dragging a Field like that should not crash it, and indeed it does not for me.

[David_McRitchie]

Crashes are frustrating, but this shouldn't be normal.

Immediate thoughts would be is this data specific or does this crash with new data?

Are we used networked folders or onedrive? If so do we get the same issue when working with a local filegeodatabase.

From this we can have a clearer idea if the issue will be more specific to the installation, data, environment or a potential software issue.

Hope that helps,

David

[JohnGuilfoyle]

"Crashes are frustrating, but this shouldn't be normal."

I've got nine Error Reports from crashes in the last two days in ArcPro on a brand new machine bought to run this software.  Crashes are extremely normal.  I add a Point Barrier to a Network Analyst route, and it shuts down. I add a Line Barrier, and it shuts down.  I draw a line in a Line Feature Class Layer, and it crashes.

I've had many over the years, sent in the reports, and I have never heard back from Esri about any of them.

[JohnGuilfoyle]

The Quintessence of Programming and Debugging:

 https://xkcd.com/1739

[JesseCloutier]

Our team would like to share a general reminder in this thread that members are expected to adhere to the Esri Community Guidelines, which require that all users demonstrate respect for each other and our solution-oriented environment by keeping their posts positive and comments constructive. In short, everyone in the Community is expected to follow our platform’s guiding principles: "Be Helpful. Be Human. Be Smart." Thank you to all those who preserve and enact those values. If there are any questions, feel encouraged to Direct Message me or email our team at esricommunity@esri.com.

[HowardWalter]

I totally agree. I just don't get why it's so popular. As a newbie, I tried sharing a CHM to use in Field Maps, but it doesn't show.  According to ArcGis help, a data type isn't supported in Field Maps.  But they don't explain which are and are not supported.   What a piece of....