Forum ‹ C# ‹ Cannot access a disposed object

[FulaFisken]

What does this mean? Does it happen because we tried to send a null value or something else?

It happens on our production server.

Code: Select all

Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'.
First seen 13 hours ago, latest 10 minutes ago. (Delete 1 error)

   at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode, AsyncCallback callback, Object state)
   at Game.ships.ShipSync.SendPlayerHeading(String playerId, Heading heading)
   at Game.ships.ShipSync.UpdateCourse(Player player, Command cmd)
   at Game.ships.ShipSync.CommandReceived(Player player, Message m)
   at Game.BaseRoom.GotMessage(Player player, Message message)
   at Game.GameRoom.GotMessage(Player player, Message message)

Thanks!

/Stefan

[FulaFisken]

We are having more of these errors now:

Code: Select all

Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'.
First seen 13 hours ago, latest just now. (Delete 1 error)

   at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode, AsyncCallback callback, Object state)
   at Game.weapons.Blaster.set_PlayerFire(Boolean value)
   at Game.ships.ShipSync.CommandReceived(Player player, Message m)
   at Game.BaseRoom.GotMessage(Player player, Message message)
   at Game.GameRoom.GotMessage(Player player, Message message)

[Oliver]

It's an error that was introduced in the last build that happens sometimes when one thread tries to send data to a user that has already disconnected.

It will be fixed in the next release, soon.

Best,
Oliver

[FulaFisken]

Thanks! <3

[Oliver]

The production servers are still slowly updating (will take hours/days), but the development server just went live (v2.2.7)