> I 100% agree with Jim but I however do not 100% agree with the bug > subject he referenced. > Bottom line is that Xorg does not currently have a way to limit its RAM > demands, but we do have a perfectly working solution for this - so why > should the X developers waste their time implementing something we > already have? > > I must agree with the comment #2 for the bug above - Xorg should rather > implement some "quota" RAM limit per Xclient. As Jim already spotted, > when we limit the whole X, the session is substantially more stable. But > it can still happen, that your gnome session, requesting only a small > piece of X server memory, will be denied and will eventually crash. With > the quota system it could never happen - you would let every single X > client to allocate some amount of resources and here you go...
Here is a link with a patch for Firefox that is supposed to help the situation: http://primates.ximian.com/~federico/news-2007-09.html#firefox-memory-1 I have not tried this yet as I don't really know the best way to implement the patch. The last few days I ran across Federico's work dating back to mid 2005. Finally here is the resulting diff he came up with: http://primates.ximian.com/~federico/misc/moz-images-20070903.diff >From what I understand this is supposed to prevent firefox from breaking >images into pixmaps and caching them in X....we'll see. Jim Kronebusch -- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
