The anon_inode:dmabuf i mention in #18 is not leaked anymore if we make ApplicationScreenshotProvider::requestImage return an empty QImage and is still leaked if we return a QImage with junk data (without calling mir::screenshot) so it seems it's not mir.
I'm investigating now if it's either qtmir, unity8, qt or it's not a fd leak at all and it's just the image cache of Qt being used.
The anon_inode:dmabuf i mention in #18 is not leaked anymore if we make ApplicationScre enshotProvider: :requestImage return an empty QImage and is still leaked if we return a QImage with junk data (without calling mir::screenshot) so it seems it's not mir.
I'm investigating now if it's either qtmir, unity8, qt or it's not a fd leak at all and it's just the image cache of Qt being used.