Stability and Memory Pressure in 8.2

[Michael Stone]

On Tue, Sep 09, 2008 at 01:10:57PM -0400, Daniel Drake wrote:
>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. 

Fine. How does the X server report failures to allocate memory on behalf
of clients? How does Browse respond?

>Such requests should never be generated, and the application crashing
>is probably the behaviour we want.

I'll grant that it may be helpful for finding the issue in the first
place, but I would much rather that we ship a Browse which displayed
what it can display without crashing.

Michael