Also a reminder that Im running this in Virtualbox, so I can fusker with a few hardware settings if I need to.Attached is output of strace of gnome-shell process that has the high CPU: strace -p 1671.
With only a web browser open, and little activity, gnome-shell is constantly using 100 CPU (as shown by top). Version-Release number of selected component (if applicable). Attached is output of strace of gnome-shell process that has the high CPU. Intellian i3 manualDowngrading (ie removing everything from -testing) didnt make the problem go away. I have not been able to reproduce the system on another machine. Occurs three times during the trace, presumably over a short period of time. So, for some reason, its constantly re-adding file-changed monitors for menu files. As a first test, can you move.configmenus away to a different location and see if that makes a difference to the problem. It seems like moving.configmenus away made the problem even worse for me. Before it rarely went over 100 - now it do that most of the time. I have for example proc1826fd19 - anoninode:inotify and strace see for example almost 2000 continues lines like. I dont know if that is what is eating cpu, but it seems suspicious. That will however at most be a trigger; it is still be a bug in gnome-shell that wrong permissions can cause something to spin this way. I tried following Mads suggestion with authconfig but couldnt get it to reduce (was there a X restart in the middle just doing gnome-shell restarts via alt-F2lgr didnt work). Vmware build kernel modulesYes, at least that. I would do a reboot after changing the pam config to make sure all components pick up the right and consistent configuration. Installed Fedora 16 as a virtual machine inside Virtualbox on a Windows 7 host a few days ago and upgraded to Fedora 17 today using preupgrade. The fixes in Bug 815413 didnt fix my issues, and I am fully up to date in yum with the patch to pam that was produced from that bugfix. Doesnt look like the only problem since creating the directories didnt drop the cpu load. Unfortunately I dont know what solved the problem: Just FYI restarting gnome-shell was not enough - i.e. Ive ran mkdir -p as suggested on those 4 directories (although I never saw that error pop up in my strace of gnome-shell), no difference. 100 Cpu Usage By Esets Daemon Ecsp How To Attach FilesUnsure how to attach files here, so heres parts of a strace I did. You are using an old initramfs that might be slightly incompatible with f17 systemd or file locations after usr-move. For the record, I was booting into the entry for 3.3.7-1.fc17.x8664 every time except that once just to look at CPU usage there.
0 Comments
Leave a Reply. |
Details
AuthorWaka ArchivesCategories |