[Bug 2524] Allocating too much pixmap memory hangs system

[bugzilla-daemon at freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=2524          
     




------- Additional Comments From kschultz at rsinc.com  2005-02-14 16:10 -------
Yes, I agree and understand about the behavior of malloc on many systems.

There still may be value in implementing an *optional* upper bound on the 
amount of pixmap storage the server can allocate.  The server can do this 
simply by keeping track of the create and destroy requests, also accounting 
for pixmaps that get destroyed when client connections drop.  The behavior of 
malloc plays no part in this tracking of pixmap storage.

The point is to give the user an alternative to allowing a client to 
completely hang the server by simply allocating pixmaps until it hangs.  Yes, 
it is the application's fault for doing this, but it is better to simply fail 
the create pixmap request so that the application can at least recover and 
prevent the lost work due to a hang that requires pulling the plug.

I know that this request is a bit close to the edge between server stability 
and application responsibility, since any app can cause this sort of resource 
usage problem.  But since the server often runs at a higher priority and needs 
to be stable, it is more than some other app or client that has run amuck.  
And this seems to be a reasonable safety measure to keep the server stable at 
the possible inconvenience of figuring out the right value to use for the 
upper limit.
          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.