#8326 BLOC 8.2.0 (: Browse causes X BadAlloc, or other crash symptoms. (was: browse causes X BadAlloc)

[Zarro Boogs per Child]

#8326: Browse causes X BadAlloc, or other crash symptoms.
-------------------------------+--------------------------------------------
   Reporter:  dsd              |       Owner:  erikos                           
       Type:  defect           |      Status:  new                              
   Priority:  blocker          |   Milestone:  8.2.0 (was Update.2)             
  Component:  browse-activity  |     Version:  Development build as of this date
 Resolution:                   |    Keywords:  8.2-759:-                        
Next_action:  diagnose         |    Verified:  0                                
  Blockedby:                   |    Blocking:                                   
-------------------------------+--------------------------------------------
Changes (by thomaswamm):

  * priority:  normal => blocker
  * next_action:  never set => diagnose
  * version:  not specified => Development build as of this date
  * milestone:  Not Triaged => 8.2.0 (was Update.2)


Comment:

 I also went to [http://wiki.laptop.org/go/Hardware_specification] using
 Browse-96 in build 8.2-759.  After a bit of scrolling the XO slowed, then
 froze for several minutes, then abruptly came back to normal life but with
 Browse shut down.  There was nothing else running aside from Journal when
 I did this test.

 I will attach the tail of /var/log/messages which shows hald invoking oom-
 killer then killing python (Browse, I presume).  This is a novice's
 interpretation, by the way.  I could be wrong.

 I suspect there are multiple bugs at play, or design deficiencies, at
 multiple levels of the XO software. The wiki page just triggers one bug
 which then cascades into a crash with variable symptoms. Good luck people!

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