gnome-settings-daemon leaking memory after idle

No answer for this bug report.
But it seems it's been fixed.
No more memory leak.

thanks closing the bug then, if it does it again it would be useful to get a log following the instructions from https://wiki.ubuntu.com/Valgrind

Same issue here over the same distribuition Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421). The system becomes laggy and unusable after several hours of idling. This happens all the times and looking through the System Monitor, gnome-settings-daemon is using up to 5 GB of RAM. I'll try to collect more info with Valgrind if i can.

Same her on Ubuntu GNOME 16.04 64-bit with GNOME 3 Team PPA. gnome-settings-daemon can eat up my 8 GB RAM after time, and then desktop 3D animations are very slow/choppy. Solution is to log out and in again.

See attachment. gnome-settings-daemon eating 65 % of my 8 GB RAM less than 24 hours after a reboot.

Running Valgrind as described here: https://bugzilla.redhat.com/show_bug.cgi?id=1321995

...I get the content in the attachment, not very helpful it seems? Also see my screenshot above.

Note: It should be noted that I run a dual monitor setup with one monitor on DVI and another on HDMI. Saw a forum post or something suggesting that it could affect it. I don't have a way to know. But it only happens on this computer, not on a Intel NUC running the same distro (but not same HW) connected to my TV.

Running Alt + F2 and then "r" to restart GNOME Shell helps speed up everything again, because AFAIK it restarts gnome-settings-daemon, but after that it still uses relatively much more RAM than after a reboot.

FIX:

Finally found a solution that does not require me to disable screen blanking and turning my monitors off physically:

1. Run dconf-editor
2. org > gnome > settings-daemon > plugins > power
3. "Set to Default" on ALL keys (this sets GNOME to never blank the screen since "sleep-inactive-ac-timeout" and "sleep-inactive-battery-timeout" defaults to 0), then UNCHECK "active", so it is false
4. Run a command at login like this: "bash -c "sleep 10 && xset dpms 0 0 900" (sleep for 10 seconds avoids GNOME taking over)
5. I also disabled the "housekeeping", "orientation" and "xrandr" plugins as they are not needed for me

I strongly suspect it has to do with my dual monitor setup (DVI and HDMI), and that the bug may exist in newer GNOME versions as well. Will check later with a live USB stick.

Cheers.

Even though I didn't do anything and it fixed itself, But I can confirm that I have a dual monitor setup. a qHD display that my Intel CPU cant support by default at max resolution and I have to use xrandr to add custom resolution on X initiation.

This bug affects me too, always on Ubuntu 16.04.

package: gnome-settings-daemon 3.18.2-0ubuntu3.1
kernel: 4.10.0-041000-generic x86_64

Steps:
1. sudo apt-get install gnome-gdb
2. G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log $(which gnome-settings-daemon) --replace