Comment 1 for bug 1227743
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
At least a part of the problem is the client holding resources from the original connection. These cannot be released as the client API gets into a "hung" state waiting for responses from a socket that died with the server.
lp:~alan-griffiths/mir/improve-tidy-up-of-mir_connection_get_display_info ensures the API eventually times out.