Frequent crashes in 2020.1.6f while debugging

I have had TONS of issues where the debugger tends to crash unity while I am inspecting different object values.

I have tried VSCode, Visual Studio Community, and Rider. They all seem to make unity stop responding after looking through object values for ~5-10 minutes. I have had this happen in various different ways, I don't really know if there is one single cause other than the length of time spent looking at the actual values in the inspectors for the respective IDE's.

I was also experiencing this in 2020.1.5f so I upgraded to 2020.1.6f but it is still happening. It seemed to crash more frequently with VSCode of the three editors/IDE's I was using, but they all had the issue.

the Unity Editor process status becomes "Not Responding" in windows and I am unable to click the main unity editor windows including the UIBuilder.

Please let me know what more information I can provide. I don't see a crash message from unity but I would be happy to provide logs if you could point me to the location that is relevant for this error.

This was the most recent error shown in the Rider console when the process hung:

Code (CSharp):

1. System.ObjectDisposedException: Cannot access a disposed object.
2. Object name: 'System.Net.Sockets.Socket'.
3.    at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
4.    at Mono.Debugger.Soft.TcpConnection.TransportReceive(Byte[] buf, Int32 buf_offset, Int32 len)
5.    at Mono.Debugger.Soft.Connection.Receive(Byte[] buf, Int32 buf_offset, Int32 len)
6.    at Mono.Debugger.Soft.Connection.ReadPacket()
7.    at Mono.Debugger.Soft.Connection.ReceivePacket()
8.    at Mono.Debugger.Soft.Connection.receiver_thread_main()

This has been causing huge headaches and I have lost significant portions of work. Please fix this.

Thanks,
Paul

 

I have the same issue since updating to 2020.3.2f1

I have tried rebuilding the project in many versions, older and newer, but it still crashes.
Also, I have tried rebuilding with different versions of the Visual Studio and Visual Studio Code packages but still get the same error.

I sent a bug report but still waiting for an answer...

 

Sorry for the late reply, didn't saw the alert until now.

So it appears that what was happening to me is somewhat different (it is a different error) but it leads to the same outcome. They moved my case to an Atlassian website and the only reference I can give as far as I can see is this number: IN-1181

Right now I have given up on TextMeshPro and are starting to port everything to UI Toolkit because I can't be having Unity randomly crashing whenever I accidentally hover a TextMeshPro internal variable.