>Also, I was able to run a few "layman" tests, and can confirm that when I have neither owncloud client nor qsynergy in the tray, the memory usage stays sane.
I think we can be pretty sure it happens with certain system tray icons.
qbittorrent spits out TootltipChanged signals once a second, the others probably do the same. Which means if there is even a tiny leak updating SNIs, it will fill up pretty quickly.
Though, I still can't reproduce locally, and valgrind showed everything being fine.
There was a fix in Qt > 5.4.1 to some QtDBus memory allocation.
Can someone confirm they still have it with that version of Qt?
Can people start a list of what apps trigger this, maybe we can find a useful pattern.
Finally, could someone with a leak capture the dbus traffic on their system whilst the memory is increasing.
ideally with bustle, or worst case dbus-monitor. Note these may contain personal information from whatever else is running, so be careful before sending.
>Also, I was able to run a few "layman" tests, and can confirm that when I have neither owncloud client nor qsynergy in the tray, the memory usage stays sane.
I think we can be pretty sure it happens with certain system tray icons.
qbittorrent spits out TootltipChanged signals once a second, the others probably do the same. Which means if there is even a tiny leak updating SNIs, it will fill up pretty quickly.
Though, I still can't reproduce locally, and valgrind showed everything being fine.
There was a fix in Qt > 5.4.1 to some QtDBus memory allocation.
Can someone confirm they still have it with that version of Qt?
Can people start a list of what apps trigger this, maybe we can find a useful pattern.
Finally, could someone with a leak capture the dbus traffic on their system whilst the memory is increasing.
ideally with bustle, or worst case dbus-monitor. Note these may contain personal information from whatever else is running, so be careful before sending.