The problem is in FF consuming all available memory on the client for
pixmaps.

In LTSP 4.2 X startup scripts there was a code that limited the X server
memory to what was actually accessible by the thin client. This code
made the X server stable because otherwise once the FF consumes all
available memory and swap, kernel kills the X server and consequently
the whole session.

I do not understand why is this code not available in ltsp-5. It was
very useful thing! With the X server being limited, the worst case you
could face was that FF crashed - but the rest of the session survived!

Increasing the swap is not a solution - bring the code I mentioned back!

Ondrej

Jim Kronebusch wrote:
> On Thu, 6 Sep 2007 15:19:27 +0300, Nadav Kavalerchik wrote
>   
>> Hi :-)
>>
>> we use firefox 2.0.0.6 on terminal's that have Intel i810 graphic display 
>> cards. we experience frequent crashes of X when browsing the net, on random 
>> sites.
>>
>> using opera / konqueror we never have problems,
>> but we miss some of the features firefox has :-(
>>
>> i remember some threads about this subject in the past, was there any
>> resolution ?
>>
>> kindly,
>> nadav :-)
>>     
>
> This actually has nothing to do with your graphic card as far as I know.  
> This is due to
> Firefox caching pixmaps to X chewing up all available system memory (RAM and 
> Swap). 
> Once firefox has consumed everything available, it will freeze your client 
> completely. 
> This appears to be the case with any mozilla based browser.  However 
> Konquerer and Opera
> do not cache the pixmaps, so they do not consume all your system memory, and 
> as a result
> you don't have any problems.
>
> So the solution is to keep cranking your Swap up, or increase your system 
> RAM, but in
> the end you will eventually run into a site that can crash your system (I 
> managed to
> find a graphic intense site that took down a client with 512MB RAM and a 1GB 
> Swap).  Or
> you can switch to an alternative browser such as Konquerer or Opera until 
> enough people
> give the mozilla guys a massive amount of heat on this and they get this 
> problem fixed,
> or at least provide a way to disable it in about:firefox (something like
> "browser.pixmap.cache enable no").
>
> Jim
>
>   


The information contained in this e-mail and in any attachments is confidential 
and is designated solely for the attention of the intended recipient(s). If you 
are not an intended recipient, you must not use, disclose, copy, distribute or 
retain this e-mail or any part thereof. If you have received this e-mail in 
error, please notify the sender by return e-mail and delete all copies of this 
e-mail from your computer system(s).
Please direct any additional queries to: [EMAIL PROTECTED]
Thank You.

-------------------------------------------------------------------------
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

Reply via email to