#8592 HIGH Not Tri: bug or feature? XO hogs CPU trying to find Mesh while already connected to Access Point

[Zarro Boogs per Child]

#8592: bug or feature?  XO hogs CPU trying to find Mesh while already connected to
Access Point
--------------------------+-------------------------------------------------
   Reporter:  thomaswamm  |       Owner:  marco                            
       Type:  defect      |      Status:  new                              
   Priority:  high        |   Milestone:  Not Triaged                      
  Component:  sugar       |     Version:  Development build as of this date
 Resolution:              |    Keywords:                                   
Next_action:  reproduce   |    Verified:  0                                
  Blockedby:              |    Blocking:  8098                             
--------------------------+-------------------------------------------------

Comment(by thomaswamm):

 I attached an strace of sugar-shell which ran for a minute or two while I
 did the following test:

  1. in Terminal, used $ top -c  to find pid of sugar-shell (1222)
  1. in Terminal, run: $ sudo strace -p 1222 >& strace.log
  1. tapped power button to suspend XO (and interrupt wlan)
  1. tapped power button to resume
  1. went to Neighborhood view and clicked on my AP as soon as it showed up
  1. after AP connected, verified in frame that both AP and Mesh icons
 showed (AP colored, Mesh still grey)
  1. returned to Terminal to ctrl-c the strace

 The strace.log is over 1 megabyte long, and incomprehensible by me.
 I did $ tar -cvjf strace.log.tar.bz2 strace.log

 The test resulted in sugar-shell hogging about 15% of CPU.  Later I did
 suspend/resume again, but let the XO automagically refind my AP. Then
 sugar-shell went down to about 3% CPU.

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