Bug Caught fatal signal - signo:11 code:1 errno:0 addr:0x20

What platform is this on? Also, are you using Unity Relay or direct IP connections?

 

Also, how is the client exiting the game? Is it a clean disconnect (calling the

NetworkManager.Shutdown

method)? Is the client just closing the application? What platform is the client on?

 

If you're able to make a server build with Burst disabled (you can do that in the Burst AOT settings), that might produce a more interesting stack trace. I'm thinking the one in your original message might be bad in some way since that

unitytls_client_get_ciphersuite_cnt

function isn't being called by the TLS send job.

 

Looking at the code on my end, I can see a scenario where a segfault would occur in the TLS layer if the connection was suddenly closed while there were packets pending to be sent.

I'll make the fix in the transport package and try to get a release going, but in the meantime if you're willing to use a customized version of the transport package (here are instructions to do so), you could patch it yourself. You'd need to add the following code at line 519-ish of

Runtime/Layers/TLSLayer.cs

:

Code (CSharp):

1. var clientPtr = ConnectionsData[connectionId].UnityTLSClientPtr;
2. // Add these lines:
3. var connectionState = Connections.GetConnectionState(connectionId);
4. if (clientPtr == null || connectionState != NetworkConnection.State.Connected)
5. {
6.     packetProcessor.Drop();
7.     continue;
8. }

 

Ah yes my apologies. I had forgotten that the connection list wasn't passed to the send job in the TLS layer. You can remedy this by adding this line at the top of the

SendJob

structure (line 495-ish):

Code (CSharp):

1. public ConnectionList Connections;

And then this line in the creation of the

SendJob

instance (line 565-ish):

Code (CSharp):

1. Connections = m_ConnectionList,

 

The fix should also be available in the last version of the transport package (2.1.0) should you wish to upgrade.