ArcGIS Pro 3.1.7 - 3.3.2 Crashing on Close with Branch Versioned Data

[lah]

Curious if anyone else has been experiencing frequent crashing of ArcGIS Pro, specifically on close of the application and while using Branch Versioned data. This started happening to us when we upgraded to 3.1.7 from 3.1.4. Recently, we did a fresh install of 3.3.2 on a new server, and the crashing is still persistent.

After saving or not saving the project, every time we hit the close button, the application freezes up and crashes. It's turning into quite an inconvenience because it is preventing locks on the data from being released properly, and I'm starting to worry about other implications or corruption.

I had a ticket open with support on it for a while, but ultimately it was closed because we could not come up with a consistent workflow that was causing it. (It happens in new and old projects, it happens in unsaved/temporary projects, it happens when viewing branch versioned data, it happens after editing branch versioned data; and once in a while, it just won't happen.) Just curious if others have been experiencing anything similar which could shed some light and help narrow down the actual issue.

[MichaelVolz]

Would it possible for you to upgrade to ArcGIS Pro 3.4 to see if this issue might be resolved there?

Would it be possible to setup a traditional versioned workflow and compare if ArcGIS Pro crashes with that setup?

[lah]

The majority of our data is traditionally versioned, and I never have issues with it. Therefore, I'm pretty confident it's related to the branch data. 

I'm unable to upgrade to Enterprise 11.4, which is the main thing keeping me from testing in 3.4.

[Robert_LeClair]

So I'm looking at your support case logged with Esri Support Services to get some insight.

- No issues working with ArcGIS Pro 3.1.4.  Note:  You can downgrade from ArcGIS Pro 3.1.7 to ArcGIS Pro 3.1.4 by going to the Window Search bar and typing view update history - this will open the View update history window.  Top left click Uninstall updates.  Navigate to the ArcGIS Pro ones and uninstall the updates back to 3.1.4 and retest your workflow.

- I see that it happens with your LRS data so maybe there's an issue with that?

- The analyst looked at the dump files and the issue appears to be fixed at ArcGIS Pro 3.2 but now is back for some reason as you mentioned.

[lah]

Hi Robert, 

Yes - I still have 3.1.4 installed on a server and it never gives me trouble. Though trying to keep our Enterprise environment up-to-date, and therefore, Pro in sync. 

- Yes, unsure if it is branch specific or LRS/APR specific. That's the only data we have branch versioned; I suppose I should spin up another database to test on some generically branched data.

- not sure we ever figured out the issue, so difficult to say if it was truly fixed, unfortunately. 

I appreciate you taking a second look at the case. If I discover anything else through testing, I will update.