#8326 NORM Not Tri: browse causes X BadAlloc

[Zarro Boogs per Child]

#8326: browse causes X BadAlloc
-----------------------------+----------------------------------------------
 Reporter:  dsd              |         Owner:  erikos       
     Type:  defect           |        Status:  new          
 Priority:  normal           |     Milestone:  Not Triaged  
Component:  browse-activity  |       Version:  not specified
 Keywords:  8.2-759:-        |   Next_action:  never set    
 Verified:  0                |     Blockedby:               
 Blocking:                   |  
-----------------------------+----------------------------------------------
 Viewing http://wiki.laptop.org/go/Hardware_specification causes us
 problems. Sometimes it crashes pretty quickly (sometimes you have to
 scroll down first) with this error:

 {{{
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 17894 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

 The page includes several images which are 4mb in compressed size, it's no
 wonder that our system struggles but it should not crash in this way.

 Adam Jackson suggests that Browse may be asking for something outside of
 X's hardcoded coordinate limits. This would suggest a xulrunner bug.
 http://lists.freedesktop.org/archives/xorg/2008-September/038157.html

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