GNOME Bugzilla – Bug 699395
gnome-settings-daemon process frequently uses a lot of CPU and RAM
Last modified: 2013-05-03 09:30:14 UTC
The gnome-settings-daemon normally uses about 5MB. Frequently, the gnome-settings-daemon process's memory usage suddenly grows to 500MB-2GB and it uses about one core (13% CPU usage on my 8-core machine, Intel i7 3770). If I kill it, the process automatically starts again, and after a while its memory/CPU usage rises again. Yesterday, I killed it at least 30 times. OS: Arch Linux I am using git master of all GNOME software (not the gnome-3.8 branch)
Can you provide the session log at least?
Where is the session log?
Try: $ journalctl _EXE=/usr/libexec/gnome-settings-daemon
Nothing: $ LC_ALL=C sudo journalctl _EXE=/usr/libexec/gnome-settings-daemon -- Logs begin at Tue 2013-04-23 01:40:07 IDT, end at Wed 2013-05-01 23:20:45 IDT. -- $ LC_ALL=C sudo journalctl _EXE=/usr/lib/gnome-settings-daemon/gnome-settings-daemon -- Logs begin at Tue 2013-04-23 01:40:07 IDT, end at Wed 2013-05-01 23:22:14 IDT. --
Run it from a terminal and get the output then. Something like: $ killall gnome-settings-daemon && /path/to/gnome-settings-daemon & You might have to do that 2 or 3 times in a row since it's racing the gnome-session auto-spawning g-s-d.
(In reply to comment #5) > Run it from a terminal and get the output then. Something like: > > $ killall gnome-settings-daemon && /path/to/gnome-settings-daemon & > > You might have to do that 2 or 3 times in a row since it's racing the > gnome-session auto-spawning g-s-d. Or simply run: /usr/libexec/gnome-settings-daemon --debug --replace
Created attachment 243106 [details] Debug
Created attachment 243122 [details] Errors
The erros: (gnome-settings-daemon:12444): color-plugin-WARNING **: failed to get info about deleted file: Error when getting information for file '/home/yosefor/.local/share/icc/.goutputstream-C0XYWW': No such file or directory (gnome-settings-daemon:12444): color-plugin-DEBUG: emit add: /home/yosefor/.local/share/icc/edid-beca4289ec92b26ff710fca1295a9128.icc (gnome-settings-daemon:12444): color-plugin-DEBUG: profile /home/yosefor/.local/share/icc/edid-beca4289ec92b26ff710fca1295a9128.icc added (gnome-settings-daemon:12444): color-plugin-DEBUG: /org/freedesktop/ColorManager/devices/xrandr_BenQ_BenQ_FP92W_1002_yosefor_1000 changed (gnome-settings-daemon:12444): color-plugin-DEBUG: need to assign display device xrandr-BenQ-BenQ FP92W-1002 (gnome-settings-daemon:12444): color-plugin-DEBUG: auto-edid profile is old, and contains no MAPPING_device_id data (gnome-settings-daemon:12444): color-plugin-DEBUG: auto-profile edid does not exist, creating as /home/yosefor/.local/share/icc/edid-beca4289ec92b26ff710fca1295a9128.icc (gnome-settings-daemon:12444): color-plugin-DEBUG: setting root window ICC profile atom from /home/yosefor/.local/share/icc/edid-beca4289ec92b26ff710fca1295a9128.icc (gnome-settings-daemon:12444): color-plugin-DEBUG: falling back to dummy ramp
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 698479 ***