ArcGIS Pro 3.5.2 hangs after several open Attribute Table's

[waterschapVallei_en_Veluwe]

After several Attribute Table actions in ArcPro 3.5.2 of feature classes in an Enterprise Geodatabase (ArcSDE 11.3) Pro hangs. I looked to the logging with <ctrl><alt>M and see a seemly infinite list of messages :

<Event time="ma sep 08 15:08:28.335" type="Info" thread="d0c: Aux CIM worker thread" elapsed="0" function="" code="">
CSharedQueue Stall timeout
</Event>

Sometimes it happens, sometimes not. But it is quite easily to reproduce. It looks like a bug. Has anyone a solution for this?

[AyanPalit]

@waterschapVallei_en_Veluwe  Correlating the 'hang' with 'CSharedQueue Stall timeout' - this seems to be a network communication issue in your ArcGIS environment. There could be a variety of factors causing this network communication like, bandwidth between Pro machine and Enterprise Geodatabase server.   

Recommend testing the same from a Pro machine on close network proximity to Geodatabase server and getting a system admin to monitor the behavior. If needed you can ask the system admin to setup SDE  intercept logging :  Set up intercept log files on a machine running ArcGIS Pro

[waterschapVallei_en_Veluwe]

Can I set the same envirionment variables on a machine where only Pro is installed. Are these envirionment variables not specific for ArcGIS Server?

[waterschapVallei_en_Veluwe]

ArcGIS Pro 3.5.2 runs in a virtual (VDI) environment. We are testing it now in a test virtual environment. The current production VDI has Pro 3.2.1. With Pro 3.2.1 we have no problems and it has the same network proximity to the Geodatabase server. So, it seems that Pro 3.5.2 causes the issue!

[waterschapVallei_en_Veluwe]

I've looked to the link about "Set up intercept log files ..." . In my case I have only to set the environment variable on my Pro machine?

[AyanPalit]

@waterschapVallei_en_Veluwe  I updated the link to generate SDEINTERCEPT log files on a machine running ArcGIS Pro. Perhaps you can compare the log files from Pro versions and determine the process that is slowing it down. Behavior on simple features should not change between Pro versions. Are you using any special/advanced layers like utility network, parcel fabric? 

[waterschapVallei_en_Veluwe]

I do not use any special or advanced layers.

[waterschapVallei_en_Veluwe]

It seems only to happen if the open Attribute Table is related to versioned (traditional full) feature classes. And maybe the combination versioned / SDO_GEOMETRY storage. With not versioned (SDO_GEOMETRY or ST_GEOMETRY) feature classes I cannot reproduce the problem!