Bug file against firefox for pixmap caches

[Jim Kronebusch]

> Thinking about it, I wonder is there an argument that this is actually an
> xserver bug more than a firefox one?
> 
> Firefox probably shouldn't behave like this, but I would have thought that
> the xserver should not allow itself to be crashed by rogue clients.  It can
> perhaps be fixed in firefox, until another application comes along which
> makes the same mistake.
> 
> Gavin

In all reality I suppose you could see this as an X server bug, a firefox bug, and a
LTSP bug.  LTSP is fixing by implementing the XRAMPERC option in Gutsy.  But you're
right, X should be smart enough to say "wait a minute there Mr. Firefox, don't you think
you're getting a little greedy?  Here, take 32MB memory and be on your way.  If you
don't like it, too bad."

And Firefox should be fixed to not to this altogether.

Check out the patch available here and see if it works.  I have never compiled a patch
in before and I don't know if I'll get time to try today.

Info:
http://primates.ximian.com/~federico/news-2007-09.html#firefox-memory-1

Patch:
http://primates.ximian.com/~federico/misc/moz-images-20070903.diff

Federico has been messing with this since sometime in 2005.  I sure hope his work paid off.

Jim

-- 
This message has been scanned for viruses and
dangerous content by the Cotter Technology 
Department, and is believed to be clean.