Still mark setUnresponsive(false) when the pings arrive late
It usually means that the client was busy and couldn't answer the ping as early as we'd hoped but there's a good chance the process is healthy again.
This commit is contained in:
parent
b5f9d9fda8
commit
e4bed6ea27
1 changed files with 2 additions and 5 deletions
|
@ -1147,11 +1147,8 @@ void XdgToplevelClient::handlePingDelayed(quint32 serial)
|
|||
|
||||
void XdgToplevelClient::handlePongReceived(quint32 serial)
|
||||
{
|
||||
auto it = m_pings.find(serial);
|
||||
if (it != m_pings.end()) {
|
||||
setUnresponsive(false);
|
||||
m_pings.erase(it);
|
||||
}
|
||||
m_pings.remove(serial);
|
||||
setUnresponsive(false);
|
||||
}
|
||||
|
||||
void XdgToplevelClient::sendPing(PingReason reason)
|
||||
|
|
Loading…
Reference in a new issue