Why does nemo eats up so much CPU (whole core on IDLE)
As you can see on the screen-dump I' using cinnamon and nemo to replace the nearly unusable (new) gnome 3 environment on FEDORA20
[juergen@nadhhlt yaze-ag-2.30.3]$ uname -a
Linux nadhhlt 3.14.9-200.fc20.x86_64+debug #1 SMP Thu Jun 26 21:23:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
top - 15:35:59 up 20:05, 5 users, load average: 0,44, 0,32, 0,26
Tasks: 251 total, 1 running, 250 sleeping, 0 stopped, 0 zombie
%Cpu(s): 1,7 us, 1,0 sy, 0,0 ni, 96,3 id, 0,3 wa, 0,2 hi, 0,5 si, 0,0 st
KiB Mem: 16325692 total, 8225136 used, 8100556 free, 888440 buffers
KiB Swap: 18440188 total, 0 used, 18440188 free, 2304068 cached
PID to signal/kill [default pid = 7031]
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7031 juergen 20 0 1866300 268644 27608 S 14,2 1,6 5:21.14 nemo
###########################################################
1249 root 20 0 277828 41716 25388 S 3,6 0,3 50:19.82 Xorg
2619 juergen 20 0 2152824 398172 47660 S 1,3 2,4 18:22.16 cinnamon
9583 juergen 20 0 814228 23500 14316 S 1,0 0,1 0:48.54 gnome-term+
1145 root 20 0 4292 596 504 S 0,3 0,0 0:09.58 rngd
1836 mysql 20 0 849568 84788 7840 S 0,3 0,5 1:18.99 mysqld
6142 juergen 20 0 123664 1708 1144 R 0,3 0,0 0:17.26 top
1 root 20 0 51068 7032 3856 S 0,0 0,0 0:06.34 systemd
But nemo takes a whole core and eats up a lot of system-resources in IDLE mode (only the desktop items will be handled, no file browser or other things are open) If nemo is running on the background, the core temperature comes um near 100°C in few minutes. After I killed nemo (desktop-buttons disappearing) the temperature degrees to 50-60°C and the system turns back to normal IDLE CPU load immediately. Any Idea or Hint?
Sincere Juergen
Make sure that all Nemo windows are closed AND make sure that no nemo processes are still running (check if it is still running using
pgrep -l nemo
. Then, open a command prompt and run nemo from there. When it takes lots of CPU, check the command prompt to see if it is printing any (error) messages repeatedly. You can also check system logs to see if any errors are reported (runjournalctl -lf
before runningnemo
and let it keep running and check if any errors are reported when you run nemo).