#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):

 In another variation, after I clicked on my Access Point icon maybe too
 much, the frame showed persistent grey AP and Mesh icons, and 'top' showed
 Network Manager and sugar-shell each taking about 45% CPU, forever.  XO
 was extremely sluggish, taking about a minute to respond to some user
 inputs. For example, a tap of the power button was followed ''about a
 minute later'' by the XO finally going into suspend.  Surprisingly, cursor
 response was good (unlike the normal 'slows').  On resume from suspend,
 the CPU hogging continued!  I eventually used Restart to get back to
 normal.

 The bottom line is, I think, that I should not be childishly mean to my XO
 by clicking too often on certain icons in Neighborhood view.

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