Hi,
a rant about browser is almost justified, they are currently the among
the worst piece of software installed on your computer. Unfortuantely,
with today's Cloud IT scenario, also quite necessary.
Most people wrote that it is a memory/CPU issue.
The CPU is at most a problem of speed with very complex pages, with
lots of AJAX and stuff (or well if you try video).
The rest is RAM. Browsers seem to throw it away.
Let me share my experience with you.
First of all: I use professionally Browsers on windows 7, all the day,
usually two/three browsers, dozens of tabs and lots of heavy pages
with javascrit/ajax although usually no plugins (flash, etc). They
rarely crash, really. Also RAM usage is high, but settles for me
around 1.5G even with lots of tabs. Rarely it passes the 2.5G mark
(note though: no videos, audio... just using cloud apps all day).
On 2014-08-23 16:31:01 +0200 Gregory Edigarov <[email protected]>
wrote:
I tried:
Firefox - bad, bad, bad. It fails 1000 times a day.
That's strange. I use Firefox on NetBSD, Mac 10.4 and on Windows 7 and
it is a fairly decent browser, although the latest revisions
(especially the new interface) . I find it reasonably stable on NetBSD
Chromium - it is better, in terms. Yes, it will not fail on the plain
place
(it is a Russian idiom, which means 'from nothing' or 'from no reason
one can
observe'), but.... left for some time it starts to be so slow... was
forced
to stay away from it too. but after all it is the only browser under
OpenBSD
that have a working lastpass plugin. (and I need lastpass, if I want
to share
my passwords between home and job computers)
I don't touch it with a pole, it comes from Google and I hate its
interface too.
Seamonkey - potentially good project. but suffers from the same
problems like
firefox. although it is fails much much less, the frequency is still
unacceptable for me.
That is my daily bread browser. I have it on:
1) windows 7, every day for work, 9 hours a day, stable as a rock
2) windows XP, "only" 1G of ram, for personal browsing, it works well,
very well... never crashes and I can even watch YouTube videos, chec
Yahoo Mail, Google mail...
3) OpenBSD and FreeBSD
the OpenBSD and FreeBSD don't have plugins... but I too get more
crashes, even if the machine is lower-spec than the obsolete windows
XP machine!
They crash on me say every second or third day.
I don't think it is "openbsd specific", but I may be wrong. If, at
least, there are issues with other BSD cousins as well.
I know, I should write to upstream mailing lists of the projects I've
mentioned above, but before that, I want to know if somebody else is
suffering such problems and I am still sure maintatiners of the
corresponding
ports will do it better than me if they find it is a problem.
"which" problems? besides getting crashes how do you distinguish the
different problems?
Do you check the core files?
I can tell for sure that on OpenBSD and FreeBSD (but linux is not so
much better, although i didn't count it in because I have the flash
plugin under linux) I have more troubles than on Windows, even Windows
XP with 1G of RAM...
Do the browsers consume more ram on Unix than on windows? are certain
components less stable? I do wonder.
I'm on holidays so i don't have access to OpenBSD, but I tried to
start seamonkey on Windows XP and FreeBSD:
just seamonkey homepage loaded: WinXP: 93.3MB, FreeBSD: 186M (112M res)
second tab with google mail open: WinXp 154M, FreeBSD: 314M (224M Res)
third tab with my blog open (*): WinXP 221M, FreeBSD: 338M (251M Res)
Wow, on FreeBSD (O need to do an OpenBSD and Linux comparison as soon
as possible) memory goes away like butter!
now I close gmail and the empty tab, just leaving my blog open: WinXP
215M, FreeBSD 331 (248M res)
now I hit the homepage button and should be "back at the beginning", I
wait for it to settle a bit: WinXP: 143M, FreeBSD 318M (237 res)
As a further note, in this state top tells me there are 29 threads
open! I'm shocked.
I'll do further test, there seem to be leaks everywhere, however for
some reason on FreeBSD Ram usage is almost twice as high sometimes...
so clearly RAM limits get hit earlier.
(*) http://multixden.blogspot.com
Riccardo
