Not sure about this now. Results are erratic. Starting a new client usually results in fd leaks but restarting the one just killed does not. Also, the "leaks" seem to be just bloat; occasionally growing, and occasionally dropping.
** Changed in: mir Status: New => Incomplete ** Changed in: mir (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1498361 Title: Android Mir servers leak fds when a client disconnects. Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Bug description: Android Mir servers leak fds when a client disconnects. This bug originated in: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1495871/comments/18 However I can now reproduce it using the Mir demo servers. So it seems to be a low level Mir bug. And only seems to happen on android, not on desktop/gbm (although we have had similar, see bug 1185183). On arale, when a client disconnects, the server gains a number of these fds: > lrwx------ 1 root root 64 Sep 22 08:34 57 -> anon_inode:dmabuf > lrwx------ 1 root root 64 Sep 22 08:34 58 -> /dev/pvrsrvkm > lrwx------ 1 root root 64 Sep 22 08:34 59 -> /dev/pvrsrvkm To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1498361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp