You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My console application using DarkRift Server 2.9.1 is randomly crashing every few hours, stating "The socket is not connected".
I'm currently using DarkRift 2.9.1 in a .NET 4.5.2 console application.
Every few hours the following error appears, crashing the whole application:
I have no idea how to reproduce or even properly debug this, as everything in the stacktrace belongs to DarkRift and not to the console application.
The server is started (from the main thread of the console application) like this:
I've tried both, the BichannelListener and the compatibility version. Both seem to have the issue.
I'm not entirely sure when exactly this started happening. Either after updating from 2.9.0 to 2.9.1, or after updating the Mono runtime on the Linux machine (Ubuntu Server 20.04) the console application is running on. It might also not be related at all, and I just didn't notice it before. (But I think everything was fine since january, until I updated the DR and Mono version in mid-march.)
The text was updated successfully, but these errors were encountered:
My console application using DarkRift Server 2.9.1 is randomly crashing every few hours, stating "The socket is not connected".
I'm currently using DarkRift 2.9.1 in a .NET 4.5.2 console application.
Every few hours the following error appears, crashing the whole application:
I have no idea how to reproduce or even properly debug this, as everything in the stacktrace belongs to DarkRift and not to the console application.
The server is started (from the main thread of the console application) like this:
I've tried both, the BichannelListener and the compatibility version. Both seem to have the issue.
I'm not entirely sure when exactly this started happening. Either after updating from 2.9.0 to 2.9.1, or after updating the Mono runtime on the Linux machine (Ubuntu Server 20.04) the console application is running on. It might also not be related at all, and I just didn't notice it before. (But I think everything was fine since january, until I updated the DR and Mono version in mid-march.)
The text was updated successfully, but these errors were encountered: