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

[gkunity123]

I am developing a game with netcode for gameobjects and i am using Unity Transport. After making the game encrypted (wss), the server crashes when the client exits the game.

Unity editor version: 2022.3.5f1
Netcode for GameObjects version: 1.5.1
Unity Transport version: 2.0.2

Caught fatal signal - signo:11 code:1 errno:0 addr:0x20
Obtained 13 stack frames.
#0 0x007f828e585520 in __sigaction
#1 0x007f829050bfb0 in unitytls_client_get_ciphersuite_cnt
#2 0x007f8289962431 in Unity.Jobs.IJobExtensions.JobStruct`1<Unity.Networking.Transport.TLSLayer.SendJob>.Execute(ref Unity.Networking.Transport.TLSLayer.SendJob data, System.IntPtr additionalPtr, System.IntPtr bufferRangePatchData, ref Unity.Jobs.LowLevel.Unsafe.JobRanges ranges, int jobIndex) → void_e4b1970fc8ecde977bccbea75c4c95e2 from UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
#3 0x007f8289962259 in f2980044d3793d86ad0f3247e0f02773_avx2
#4 0x007f8289989aca in f2980044d3793d86ad0f3247e0f02773
#5 0x007f828fc2eeea in ExecuteJob(ManagedJobData*, void ()(void, void*, void*, void*, int), int, unsigned char*)
#6 0x007f828fc2dcc0 in ForwardJobToManaged(ManagedJobData*)
#7 0x007f828fc2ac66 in ujob_execute_job(ujob_control_t*, ujob_lane_t*, ujob_job_t*, ujob_handle_t, int)
#8 0x007f828fc2b5e4 in lane_guts(ujob_control_t*, ujob_lane_t*, int, int)
#9 0x007f828fc2c565 in worker_thread_routine(void*)
#10 0x007f829002d9bd in Thread::RunThreadWrapper(void*)
#11 0x007f828e5d7b43 in pthread_condattr_setpshared
#12 0x007f828e669a00 in __xmknodat

[simon-lemay-unity]

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

[simon-lemay-unity]

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?

[gkunity123]

@simon-lemay-unity

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?

Server Platform: Linux
Client Platform: WebGL
Connection Type: Direct IP Connection(with wss://domain:port with A Record)
I get the error when the user just closes the application directly.

[simon-lemay-unity]

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.

[simon-lemay-unity]

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:

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

[gkunity123]

@simon-lemay-unity

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:

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

Thank you for the help.

[gkunity123]

@simon-lemay-unity

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:

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

[simon-lemay-unity]

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):

public ConnectionList Connections;

And then this line in the creation of the SendJob instance (line 565-ish):

Connections = m_ConnectionList,

[zhare86]

Thanks, I’ve run into this as well and fixed it for the time being with the code snippet above.

[simon-lemay-unity]

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

[dan_ginovker]

Will this be fixed in 1.4.x? 2.x is only available on newer editors Migrating from 1.X | Unity Transport | 2.0.2

[simon-lemay-unity]

Are you seeing the issue with 1.4.0? The error reported here was for code that only exists in 2.X. I would not expect this error to occur in the 1.X version of UTP. If it does, we’d need a detailed stack trace to investigate what’s happening.