ArcPro 3.2.0 Crashing When Changing Symbology

[TraceyLeet]

A colleague is having trouble with ArcPro crashing whenever he wants to change symbology. He has a layer of lines symbolized in graduating colors and if he attempts to make any adjustment to the symbology, ArcPro crashes. For instance, if he tries to adjust the width of all the line classes at once, it crashes. He has also tried to change the symbology of one class and it still crashes. The layer in question is in a local gdb, not our organization's sde. This seems to me to be behaving very similarly to the 2.9 bug but he is already on version 3.2.0. I haven't been able to find any bugs for 3.2.0 related to this so I was wondering if anyone else has had this issue or any troubleshooting tips. Thanks!

[JesseCloutier]

Hi @KirkMason and @JodiFlory, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

[JodiFlory]

SO FRUSTRATING.  Crashes on symbology changes are constant for me lately, I experienced the bug reported in 2.9.2 a couple years ago, the patch fixed it for me, but it seems to have resurfaced?  I upgraded to 3.4 and the problem seems worse.  I'm back to ArcMap.  Please fix this ESRI!