#10386 NORM Not Tri: Memory leak in sugar-session process

[Zarro Boogs per Child]

#10386: Memory leak in sugar-session process
---------------------------------------+------------------------------------
           Reporter:  martin.langhoff  |       Owner:  dsd                                    
               Type:  defect           |      Status:  new                                    
           Priority:  normal           |   Milestone:  Not Triaged                            
          Component:  sugar            |     Version:  1.5/1.0 Software Build os852 aka 10.1.2
         Resolution:                   |    Keywords:                                         
        Next_action:  never set        |    Verified:  0                                      
Deployment_affected:                   |   Blockedby:                                         
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by martin.langhoff):

 Using Guppy based on http://wiki.laptop.org/go/Memory_leak_testing

 it's clear we're leaking objects referred to the UI representation of the
 access points.

 `iwlist scan ` spots 37 APs, and that's roughly what you see in the
 UI. Some with weak signal appear and disappear --

 Using heapy, I see that the top 3 entries have
 120, 120 and 363 objects, and they grow "in concert".  When I "dump"
 the entries of the top one with .theone, the object looks like a UI
 widget for an AP. If I do

 for n in range(120):
    hp.heap()[0].byid[n].theone['_primary_text']

 what I see is the ESSIDs of the APs -- repeated multiple times.

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