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 739707 - GNOME Control Center's Bluetooth settings (gtk spinner?) causes a ton of wakeups and heats up the CPU
GNOME Control Center's Bluetooth settings (gtk spinner?) causes a ton of wake...
Status: RESOLVED DUPLICATE of bug 732199
Product: gtk+
Classification: Platform
Component: .General
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-11-06 04:47 UTC by Jean-François Fortin Tam
Modified: 2014-11-09 19:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot - without the spinner/discovery (326.75 KB, image/png)
2014-11-06 04:47 UTC, Jean-François Fortin Tam 		Details
screenshot - with the spinner/discovery (262.06 KB, image/png)
2014-11-06 04:49 UTC, Jean-François Fortin Tam 		Details
sysprof output (126.50 KB, application/gzip)
2014-11-07 18:52 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2014-11-06 04:47:58 UTC 
Created attachment 290069 [details]
screenshot - without the spinner/discovery

On a Core i7, if I leave gnome control center's Bluetooth panel running, I eventually hear my thinkpad's fan start to scream because of excess heat (usually it's dead silent), indicating that the CPU is being awakened quite a bit.

Attaching some screenshots.
Comment 1 Jean-François Fortin Tam 2014-11-06 04:49:42 UTC 
Created attachment 290070 [details]
screenshot - with the spinner/discovery

As you can see here you suddenly end up with 10-15% constant CPU use, go from 230 to 630 CPU wakeups per second, and from 3 to 50 GPU wakeups per second.

Wondering if that's the bluetooth panel doing that, or the gtk spinner animation.
Comment 2 Bastien Nocera 2014-11-06 10:00:28 UTC 
Try using sysprof to find out.
Comment 3 Rui Matos 2014-11-06 18:08:10 UTC 
I'm pretty sure this is a gtk+ thing. I get something like that with gtk3-widget-factory. In fact I don't think this is strictly a bug, something has to change those pixels and make them reach the screen... of course, there might be inefficiencies along the way.
Comment 4 Jean-François Fortin Tam 2014-11-07 18:52:34 UTC 
Created attachment 290199 [details]
sysprof output

DAT SYSPROF!
Comment 5 Matthias Clasen 2014-11-07 22:06:23 UTC 
'wakeups' - not a bug. If you want to render a smooth animation, you have to deliver a frame 60 times a second, no way around it.
Comment 6 Matthias Clasen 2014-11-07 22:08:36 UTC 

*** This bug has been marked as a duplicate of bug 732199 ***
Comment 7 Jean-François Fortin Tam 2014-11-09 19:36:24 UTC 
If it was only waking up the GPU... but it's creating 400 CPU wakeups in the process, are you sure that's normal?