#8347 BLOC 8.2.0 (: 5 instances of Clock Activity eventually all die (from oom-killer ?)

[Zarro Boogs per Child]

#8347: 5 instances of Clock Activity eventually all die (from oom-killer ?)
-------------------------------------+--------------------------------------
   Reporter:  thomaswamm             |       Owner:  dsd                              
       Type:  defect                 |      Status:  new                              
   Priority:  blocker                |   Milestone:  8.2.0 (was Update.2)             
  Component:  stability-reliability  |     Version:  Development build as of this date
 Resolution:                         |    Keywords:                                   
Next_action:  reproduce              |    Verified:  0                                
  Blockedby:  7579                   |    Blocking:                                   
-------------------------------------+--------------------------------------

Comment(by cscott):

 The last log says olpc-update-query triggered the OOM killer, but it
 doesn't seem to have been the 'big' process that got killed.  My review of
 olpc-update-query doesn't indicate any place that should be allocating a
 lot of memory; I think it was just the 2M or so which the python
 interpreter wants that tipped the system over the edge.

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