Hide Forgot
Created attachment 365027 [details] full gdb log Description of problem: I left my gnome session running overnight and all I found in the morning was the login screen again (=must have crashed, I'll try to report that too, but there is nothing interesting in the logs). I logged in again and found metacity using 100% cpu. A backtrace of the running process shows: (gdb) thread apply all bt Thread 1 (Thread 0x7f3fc1f45800 (LWP 21756)): #0 0x0000003b4dcd7fa8 in __poll (fds=0xf396b0, nfds=7, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 #1 0x0000003b4f43c9fc in g_main_context_poll (n_fds=<value optimized out>, fds=<value optimized out>, priority=<value optimized out>, timeout=<value optimized out>, context=<value optimized out>) at gmain.c:2904 #2 g_main_context_iterate (n_fds=<value optimized out>, fds=<value optimized out>, priority=<value optimized out>, timeout=<value optimized out>, context=<value optimized out>) at gmain.c:2586 #3 0x0000003b4f43d065 in IA__g_main_loop_run (loop=0xe53080) at gmain.c:2799 #4 0x000000000042b30e in main (argc=1, argv=0x7fff1e2f63a8) at core/main.c:599 (gdb) q Version-Release number of selected component (if applicable): metacity-2.28.0-1.fc12.x86_64 How reproducible: Unknown, it happened the first time.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
If this happens again, what would be useful would be A) sampling multiple times with continue then hitting control-c until it is doing something other than the above (which is just waiting in the mainloop) B) if that doesn't work, then the a short snippet of running 'strace' on the process C) The output of ls -l /proc/<metacity pid>/fd
I can't reproduce this any more, so no point in keeping it open. Probably one of the updates fixed it.
Facing 100% utilization for metacity process on RHEL 5.11 uname -a Linux xxxxxxxxxxxxxxxxxxxx 2.6.18-398.el5 #1 SMP Tue Aug 12 06:26:17 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux [xxxxxx@xxxxxxxxxxxx cups]# ls -ltr /proc/22008/fd total 0 lrwx------ 1 root root 64 Apr 28 11:20 9 -> socket:[219290680] l-wx------ 1 root root 64 Apr 28 11:20 8 -> pipe:[219290679] lr-x------ 1 root root 64 Apr 28 11:20 7 -> pipe:[219290679] l-wx------ 1 root root 64 Apr 28 11:20 6 -> pipe:[219290678] lr-x------ 1 root root 64 Apr 28 11:20 5 -> pipe:[219290678] l-wx------ 1 root root 64 Apr 28 11:20 4 -> pipe:[219290677] lr-x------ 1 root root 64 Apr 28 11:20 3 -> pipe:[219290677] l-wx------ 1 root root 64 Apr 28 11:20 2 -> /root/.vnc/xxxxxxxxxxxxxxxxxxxx:1.log lrwx------ 1 root root 64 Apr 28 11:20 15 -> socket:[251966155] lrwx------ 1 root root 64 Apr 28 11:20 14 -> socket:[238959999] lrwx------ 1 root root 64 Apr 28 11:20 13 -> socket:[219290693] lrwx------ 1 root root 64 Apr 28 11:20 12 -> socket:[219290688] lrwx------ 1 root root 64 Apr 28 11:20 11 -> socket:[219290686] lrwx------ 1 root root 64 Apr 28 11:20 10 -> socket:[219290683] l-wx------ 1 root root 64 Apr 28 11:20 1 -> /root/.vnc/xxxxxxxxxxxxxxxxxxxx:1.log lr-x------ 1 root root 64 Apr 28 11:20 0 -> /dev/null