#8711 BLOC Not Tri: Sugar-shell burning up cumulative 1-2% of CPU resources after every Activity launch/resume

[Zarro Boogs per Child]

#8711: Sugar-shell burning up cumulative 1-2% of CPU resources after every
Activity launch/resume
---------------------------+------------------------------------------------
   Reporter:  garycmartin  |       Owner:  marco                            
       Type:  defect       |      Status:  new                              
   Priority:  blocker      |   Milestone:  Not Triaged                      
  Component:  sugar        |     Version:  Development build as of this date
 Resolution:               |    Keywords:  blocks:8.2? r?                   
Next_action:  review       |    Verified:  0                                
  Blockedby:               |    Blocking:                                   
---------------------------+------------------------------------------------

Comment(by tomeu):

 See line 2032 at
 http://svn.gnome.org/viewvc/pygobject/tags/PYGOBJECT_2_14_2/gobject/gobjectmodule.c?view=annotate
 .

 That adds a reference to the bound method that will be only released when
 the timeout is destroyed, that means when the callback returns False or
 gobject.source_remove(self._pulse_hid) is called.

 So we need to stop/remove all idle and timeout handlers if we want those
 instances to be released.

-- 
Ticket URL: <http://dev.laptop.org/ticket/8711#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system