On Tue, 2008-09-09 at 00:10 -0400, Michael Stone wrote: > - whether we can get Browse to behave intelligently when it receives > BadAlloc errors from X?
I have no doubt that Browse/xulrunner has room for improvement with memory usage but this is not where you should be looking. These BadAlloc messages are true errors generated when the application requests pixmaps outside of the coordinate range accepted by X (this is well documented). This is a real bug in the code, not a memory pressure issue. Such requests should never be generated, and the application crashing is probably the behaviour we want. Daniel _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
