I find Pro 3.3.x to be a bit more unstable than 3.1 or 3.2.
With unstable I mean likely to crash, or have some screen corruption and take a long time to return to the user for input.
This does not include waiting for 'large' datasets to process or similar.
This post is to create a list of tasks where you should save everything before you attempt to start doing them; although they seem benign at face value.
For me the most likely thing to cause such breakage is to change symbology a lot in the "Unique Values" pane.
Being in a layout and testing what looks best at the specific scale and with the legend visible I find that I should click away from the Symbology tab every now & then to have it reload for other layers. If I don't do this it will likely throw a tantrum if I make too many changes.
I have Auto Apply on.
The symbol list can be quite small - recent case only 8 entries.
Behaviour:
I can change a couple of symbols, line & fill styles with basic colour, thickness & alpha, and at some point the interface will just not come back (i.e. allow for user input again) after one of the changes.
In some cases, if you click onto the map window (away from the layout), it will come back. If you click Save, it will complete the save and come back a minute or so later.
After saving and waiting for it to start responding again, I can continue working as if nothing happened, unless I make too many changes to the symbology again.
It hard crashes very infrequently during this period of self discovery.
I wonder of it is related to:
https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-polyline-symbology-error-quot-requeste...
If you're still reading:
In the past "unstable" was also used to indicate frequently changing software versions or releases - signifying that you may run into compatibility issues etc, not just be buggy or have it likely to crash. The word "volatile" was also used in this context.
It feels to me as if Pro is suffering from being unstable, in both domains of the word, due to being rapidly developed without maintaining a release stream approach.
To put it in the Debian vernacular - Pro should use streams of Stable, Testing, Unstable, Experimental so users can be risk averse or accept the risk and adopt new features as a choice.
