Nadav Kavalerchik wrote: > i think i solved it with all of your helpful advices! , thanks you :-) > > the script that Ondrej suggested i use was already in startx but was > never used by me. > so i set the XRAMPERC to 80 and found out that when i overload FF with > 20 tabs that hold flash objects and heavy graphics the FF crashes > alone and leaves the X and the desktop in one piece :-) which > usually...used to crash the entire session and made the terminal hang. > > thanks again ! > (i hope it solved for now) > > maybe i should also report a bug about this to the Xorg bugzilla ?
There's already a bug on this. I opened it a couple of years ago. https://bugs.freedesktop.org/show_bug.cgi?id=4942 But, what's the Xserver to do? Deny allocating any ram to the Xclient? that's what the XRAMPERC does. The problem is, all of the Xclient applications, such as Firefox don't gracefully handle the denial on the ram request. They die a horrible death. Not the kind of behaviour you'd like. If applications paid a bit more attention to the resources they consume, then this problem wouldn't happen. In firefox's case, when you go to a page that has lots of graphics, Firefox sends ALL of the images to the Xserver in anticipation of displaying them later. But, if you never scroll down the page, the graphics never need to be displayed, so sending the images turns out to be a waste. If you click the 'Back' button, firefox will tell the Xserver to destroy those pixmap objects and the memory is released to the OS. BUT, if you click a link in a page, the Xserver doesn't do that, again, it is anticipating that if you moved forward through a page, then you'll possibly be returning to that page. it does this, because it wants to appear very fast. if everytime you scrolled down the page, it had to worry about whether there's anything being revealed that hasn't been sent to the xserver, then firefox might appear slow. Personally, I like the idea of it having a "fast mode". i just wish it was optional. Just a note about using XRAMPERC. Once the Xserver allocates up to the limit, it will refuse to allocate ram to ANY application. SO, lets say Firefox chews up the bulk of the ram with pixmap caching. then, you want to open another program, like the Gimp. BLAMMO! the Xserver refuses the request and the Gimp dies. Another example is if you are VERY close to the limit of ram allocation. You click on the 'Applications' menu in Gnome. that needs to allocate a small amount of ram. BLAMMO ! Gnome crashes. Believe me, these things happen. It's not a pretty sight. Anyway, I hope the above rambling makes some sense. Jim McQuillan [EMAIL PROTECTED] ------------------------------------------------------------------------- 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
