GNOME Bugzilla – Bug 660211
CPU usage increases dramatically to 99% while switch between Overview and Window.
Last modified: 2013-02-09 17:27:30 UTC
CPU usage increases dramatically to 99% while switch between Overview and Window. Configuration details: 1.CPU:Intel(R) Atom(TM) CPU N570 @1.66GHz 2.HDD:250G(Sector size:512B) 3.RAM:1G Steps to reproduce the bug: 1.Let system idle to make sure CPU is on normal status(0.3%); 2.Hover(using Mouse) on Activities,switch between Overview and Window,do this about 5 times/5 seconds,and CPU usage increases to 90%; 3.Wait for 5 seconds,then the CPU down to normal status.
Looks like that this is just the GC.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 197856 [details] Gnome-Shell_Strace log Update the Gnome-Shell Strace Log. Thanks
(In reply to comment #1) > Looks like that this is just the GC. What is GC?
(In reply to comment #4) > (In reply to comment #1) > > Looks like that this is just the GC. > > What is GC? The garbage collector (it runs to find unused stuff and frees memory). As for your trace, create a stacktrace using gdb, the strace output isn't really useful.
Cause no Crash,no Stacktrace.
My understanding is right?
(In reply to comment #6) > Cause no Crash,no Stacktrace. (In reply to comment #7) > My understanding is right? No you can create a stacktrace at any time. Just attach gdb to the process (while it is using 99% cpu in that case) and create one.
Oh,when I press Ctrl+C after run --replace in gdb gnome-shell,Terminal hanged,so command"thread apply all bt full" cannot be typed,the backtrace cannot be generated.
Cause CPU usage is too high. So any other method to generate the backtrace? Thanks a lot.
Try gstack.
Created attachment 199600 [details] gstack log attach gstack log,Thanks!
Yeah, mutter is just polling. Are you sure you grabbed the stack trace at the right time?
Hi Alex, could you answer the last question, and check if this still occurs with GNOME 3.6?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!