Dashmap get_mut sometimes block thread

[Kumassy]

In certain situation, get_mut exhausts entire CPU.

ownserver/proxy_server/src/store.rs

Lines 22 to 29 in 9830786

	match self.clients.get_mut(&client_id) {
	Some(mut client) => {
	client.send_to_client(packet).await
	},
	None => {
	Err(ClientStreamError::ClientNotAvailable(client_id))
	}
	}

Use try_get_mut of DashMap 5
https://docs.rs/dashmap/latest/dashmap/struct.DashMap.html#method.try_get_mut

[Kumassy]

In async code, dashmap sometimes causes deadlock

This is a known issue. It stems from the fact that you are keeping a Ref guard bound to _ across an await point which may deadlock. The v4 release does fix this issue and will be coming out in May.

xacrimon/dashmap#79

DashMap 5.3.4 still have the problem, so we should use RwLock<HashMap<K,V>> for now.

[x1957]

In async code, dashmap sometimes causes deadlock

This is a known issue. It stems from the fact that you are keeping a Ref guard bound to _ across an await point which may deadlock. The v4 release does fix this issue and will be coming out in May.

xacrimon/dashmap#79

DashMap 5.3.4 still have the problem, so we should use RwLock<HashMap<K,V>> for now.

Does 5.4 still have the problem?