Yeah I prefer a minimialist approach too, and tabs are a must for me for
browsing, so that's why IE7 > IE6.
And it's exactly like Chris says; when the program you have open starts out
by using 100 or so MB of mem, but then after opening multiple windows and or
leaving them open for a while (which I often do) the program might grab few
hundreds, or even over 1GB of mem, and then run out of virtual mem and then
things just crawl and die at that point...
That's normal for IE from what I understand. The other issue is that
opening more than one or two pages with Flash (like YouTube) at once causes
CPU to spike (does on my laptop and even my desktop). Anyone else run into
this and know a fix?
BINO
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Christopher Fisk
Sent: Friday, January 23, 2009 2:04 PM
To: [email protected]
Subject: Re: [H] IE7 problem
On Fri, 23 Jan 2009, DHSinclair wrote:
> Bino,
> Let's just agree to disagree then. For me, IE7 just stinks, period.
> IE6sp1 is fine in either the W2K version or the XP version. Yes, I have
been
> schooled, cajoled, prattled at, and scolded into certain necessary tricks
to
> "harden" IE. Certainly not perfect, but so far so good.
>
> Then again, of course, I am not browser-centric either.
>
> Can you expand on the "memory leak issues?" Many in the collective
> now use FF and I do not recall hearing about this. What exactly is a
> "memory leak" anyway?
> Thanks,
> Duncan
Meh, my order of Preference is FF3 > FF2 > IE7 > IE6.
Tabs are a must, and IE6 doesn't support them out of the box.
The memory leak isn't a leak per say, it's just that the way firefox is
written it caches stuff. a LOT of stuff. If you have firefox open and
rarely close it (I am like that at work -- restart firefox every couple of
WEEKS) and run with a bunch of tabs (6+ or more) you'll run into instances
where firefox grows to use all the available memory on the system.
It can be controlled by doing various tweaks, but mostly it's just a
matter of minimizing it and restoring it.
Christopher Fisk
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
