...before I applied that patch "dunst" RSS increased permanently with about 70MB every time I switched songs in Spotify for Linux. Running notify-send lots of times in a script didn't trigger the bug, it's only certain notifications that trigger the leak and Spotify seems to be sending these particular notifications.
I noticed this because my dayjob compilation started to freeze my machine (despite having 18GB RAM). This monday when I got to work my machine was really slow and kswap0 was taking 100% in kernel threads. Turns out "dunst" had 41GB mapped and 16GB RSS at that point because I had accidentally left spotify running over the weekend.
Adding the g_variant_unref(content); call that catharsis suggests in the upstream bug worked well for me and dunst no longer leaks. I'm attaching a copy of this patch here as well.
I also thought it was issue #172 at first but applying that patch didn't help much for me. What did help was this one: /github. com/knopwob/ dunst/issues/ 173
https:/
...before I applied that patch "dunst" RSS increased permanently with about 70MB every time I switched songs in Spotify for Linux. Running notify-send lots of times in a script didn't trigger the bug, it's only certain notifications that trigger the leak and Spotify seems to be sending these particular notifications.
I noticed this because my dayjob compilation started to freeze my machine (despite having 18GB RAM). This monday when I got to work my machine was really slow and kswap0 was taking 100% in kernel threads. Turns out "dunst" had 41GB mapped and 16GB RSS at that point because I had accidentally left spotify running over the weekend.
Adding the g_variant_ unref(content) ; call that catharsis suggests in the upstream bug worked well for me and dunst no longer leaks. I'm attaching a copy of this patch here as well.