Comment 31 for bug 1495871

Note that tools like valgrind (memcheck) are unlikely to find the problem. Because C++ and RAII... the offending resources get released on shutdown and never actually leaked. So instead of leaks, you have to hunt for "bloat" and use a memory/resource profiler.

I got distracted for a long time finding lots of similar but unrelated erratic bloat in Mir demo servers on Android. But I think those are specific to Mir demos and not Unity8. Seems plausible Unity8 is possibly avoiding some Mir logic that's bloaty in its own right.

Next stop: Rebuild a qtmir development environment and investigate the snapshot stuff. In theory if the snapshot code is leaking a buffer then that would explain the anon_inode:dmabuf handle. However it's not just the snapshot code but also bug 1498816 and how that affects SessionMediator that's concerning.