After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660211 - CPU usage increases dramatically to 99% while switch between Overview and Window.
CPU usage increases dramatically to 99% while switch between Overview and Win...
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: general
3.1.x
Other Linux
: High critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-27 02:40 UTC by alex
Modified: 2013-02-09 17:27 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Gnome-Shell_Strace log (74.88 KB, text/x-log)
2011-09-30 09:07 UTC, alex 		Details
gstack log (3.39 KB, text/x-log)
2011-10-21 01:34 UTC, alex 		Details

Description alex 2011-09-27 02:40:24 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.
Comment 1 drago01 2011-09-29 13:52:05 UTC 
Looks like that this is just the GC.
Comment 2 Colin Walters 2011-09-29 14:42:13 UTC 
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!
Comment 3 alex 2011-09-30 09:07:05 UTC 
Created attachment 197856 [details]
Gnome-Shell_Strace log

Update the Gnome-Shell Strace Log.
Thanks
Comment 4 alex 2011-10-11 06:26:08 UTC 
(In reply to comment #1)
> Looks like that this is just the GC.

What is GC?
Comment 5 drago01 2011-10-11 06:32:50 UTC 
(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.
Comment 6 alex 2011-10-17 07:00:50 UTC 
Cause no Crash,no Stacktrace.
Comment 7 alex 2011-10-17 07:01:24 UTC 
My understanding is right?
Comment 8 drago01 2011-10-17 07:05:16 UTC 
(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.
Comment 9 alex 2011-10-17 09:35:05 UTC 
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.
Comment 10 alex 2011-10-17 09:36:32 UTC 
Cause CPU usage is too high.
So any other method to generate the backtrace?
Thanks a lot.
Comment 11 Jasper St. Pierre (not reading bugmail) 2011-10-17 11:37:57 UTC 
Try gstack.
Comment 12 alex 2011-10-21 01:34:53 UTC 
Created attachment 199600 [details]
gstack log

attach gstack log,Thanks!
Comment 13 Jasper St. Pierre (not reading bugmail) 2011-10-21 01:37:00 UTC 
Yeah, mutter is just polling. Are you sure you grabbed the stack trace at the right time?
Comment 14 Jean-François Fortin Tam 2012-10-25 20:14:25 UTC 
Hi Alex, could you answer the last question, and check if this still occurs with GNOME 3.6?
Comment 15 Tobias Mueller 2013-02-09 17:27:30 UTC 
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!