ArcGIS Pro 3.6 crashing with labels operations

Question

Issue:

ArcGIS Pro 3.6 (and when rolled back to 3.5.5) crash when conducting label operations in numerous existing maps (e.g., making symbology changes within label class window or selecting layers in label view of TOC). None of these maps use the same fonts as the other maps, and many maps only use stock Windows fonts.

Background:

I updated a laptop with 3.5.5 on it to 3.6 by uninstalling 3.5.5  and installing 3.6. I did not do a "clean install" by renaming existing folders. After the update to 3.6, when interacting with labels in numerous existing maps, the program crashed. The font and styles of labels in the maps that crashed in 3.6 had never crashed with 3.5.5. I then did a soft reset on 3.6 (https://support.esri.com/en-us/knowledge-base/how-to-perform-an-arcgis-pro-soft-reset-000027631). The maps continued to crash. I then did a clean uninstall of 3.6 to roll back to a clean install of 3.5.5 (https://support.esri.com/en-us/knowledge-base/how-to-perform-a-clean-uninstall-and-reinstall-of-arcgi-000030419). The maps continued to crash.

I then installed 3.6 on a new machine (different GPU, newer OS version) which has never had any Arc products installed. The same existing maps continued to crash when undertaking label operations and existing maps that I hadn't previously opened on the 3.6 install of the laptop are now crashing as well.

I cannot seem to replicate the crashing in a fresh Pro project. I have submitted error reports, but I have a Personal Use license, so can't submit an Esri case.

Robert_LeClair · Answer

Based upon your findings (excellent by the way), I would highly recommend you contact Esri Support Services to log a case.  This is likely your best approach in either logging this as a BUG and/or finding a solution to the issue.

VenkataKondepati · Answer

Hi @AK_Mapplications,

This is an excellent repro. Thank you for taking the time to isolate it.

Based on your testing, this strongly points to a core labeling/rendering bug with picture-filled text symbols, not project corruption or upgrade artifacts. The fact that it reproduces in brand-new projects, across multiple Pro versions (3.5.x–3.6), machines, licenses, and data sources rules out environment issues and makes this very actionable for Esri engineering.

Key takeaway: crashes are triggered by switching layers in the TOC when multiple label classes use picture fills, with probability increasing as more layers are involved.

At this point, this should be logged as a defect with Esri Support (or via internal escalation if available), referencing:

* Picture fill text symbols

* Label Class UI / TOC interaction

* Repro steps you outlined (they’re very solid)

In the meantime, the only practical workaround is to avoid picture-filled text symbols across multiple labeled layers in the same map.

This is exactly the kind of detailed repro that helps get an issue fixed — nicely done.

AK_Mapplications · Answer

@Robert_LeClair @VenkataKondepati After more testing, I am now able to replicate the issue in new projects with new maps on three separate computers quite easily. It appears to happen when using a text fill symbol that is a Picture fill. I've tested this out by downloading a fresh copy of Natural Earth data to anywhere on a C drive or external hard drive, downloading a style with a text picture fill (like John Nelson's WPA Poster Style) or choosing a newly downloaded small (<2040px) image from a place like Unsplash, and labeling 3 or more feature classes with a picture fill. Then, within the Label tab of the Table of Contents, switching selections between different layers. If there are more than 3 layers with picture filled labels, selecting layers in the Drawing Order tab of the TOC will eventually also cause a crash, with the likelihood of a crash increasing with the number of labeled layers.

I tested this out on a laptop that had been upgraded from 3.5.5 to 3.6; on a desktop with 3.6 that never had Pro on it before; and on a company-administrated laptop with 3.5.2 that never had Pro on it before (not personal license), and was easily able to cause the crash within a few mouse clicks each time.