Comment 30 for bug 1495871

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Mir does associate resources with a client socket that are not released until one of two things happen:

1. The client explicitly disconnects
2. An operation (like the outstanding read attempt) on the socket reports an error

AFAIK there is no *guarantee* that the latter happens in a timely manner when a client disconnects abruptly.