--- Rob Keeling wrote:

We are seeing frequent freeze ups while browsing the web, leaving stuck processes that need be killed.

An indication as to their state when the freeze is of importance here: ps aux | awk '/Z/ {print $11}' ps aux | awk '/D/ {print $11}' This would help us determine if the process is merely zombing is really is being killed. Galeon isn't segfaulting is it?

Other than nightly reboots, are there any other low processor load browsers that might be better than Galeon or do we just need a newer version?

Galeon is far too over-loated, relying on the core set of GNOME libs to get the damn thing going. Mozilla-firebird is quite good, I would go with that. There is also dillo , but that is not quite as featureful.

I have been using Mozilla Firebird on our win32 boxes, does this work well with ltsp?

I think you're confusing the issue. LTSP provides a means to an end. Having your web-browser freeze like that is not really related, IMO. -- Thomas Adam ===== "The Linux Weekend Mechanic" -- http://linuxgazette.net "TAG Editor" -- http://linuxgazette.net "<shrug> We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :)" -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ________________________________________________________________________ BT Yahoo! Broadband - Free modem offer, sign up online today and save £80 http://btyahoo.yahoo.co.uk

On Tuesday 27 January 2004 19:10, Thomas Adam wrote:

Galeon is far too over-loated, relying on the core set of GNOME libs to get the damn thing going. Mozilla-firebird is quite good, I would go with that.

I haven't tried Firebird on LTSP but I suspect it may perform worse than Galeon. My experience is with Mozilla, but the reasoning is the same: For Mozilla and Firebird, the user interface uses XUL, whereas Galeon uses 'real code' (even if it is bloated). Consequently, when multiple instances of Galeon are running, all this code is shared, whereas with Mozilla and Firebird, the user interface code is interpreted separately, and stored separately in memory for each instance. This made a dramatic difference in the memory demands on the server for us . Sorry I can't remember how much, but it was an extremely significant improvement when we moved from Mozilla to Galeon. Cheers -- Phil Driscoll

On Tue, 2004-01-27 at 19:30, Phil Driscoll wrote:

On Tuesday 27 January 2004 19:10, Thomas Adam wrote:

...

Galeon is far too over-loated, relying on the core set of GNOME libs to get the damn thing going. Mozilla-firebird is quite good, I would go with that.

I haven't tried Firebird on LTSP but I suspect it may perform worse than Galeon. My experience is with Mozilla, but the reasoning is the same: For Mozilla and Firebird, the user interface uses XUL, whereas Galeon uses 'real code' (even if it is bloated). Consequently, when multiple instances of Galeon are running, all this code is shared, whereas with Mozilla and Firebird, the user interface code is interpreted separately, and stored separately in memory for each instance. This made a dramatic difference in the memory demands on the server for us .

This is interesting. Have you or has anyone else tried Epiphany? It was started also by Marco Pesenti Gritti (apologies if I spelled that incorrectly) after he moved on from Galeon, and seems lighter and faster than Galeon, whilst not being based on the XML User Interface, so should be able to take advantage of code sharing, like Galeon.

Sorry I can't remember how much, but it was an extremely significant improvement when we moved from Mozilla to Galeon.

Cheers -- Phil Driscoll