Hi Bob,
It is a beta product. Already there have been reports of high memory usage
on certain sites that are using a large number of absolutely positioned divs
or other layout standards reasons.
You should be able to identify yourself which sites are chewing up memory
and add those sites to your Compatibility list (Tools>Compatibility View
Settings) so that they render using the IE7 emulation instead of IE8
standards.
IE8 Beta 2 is near the end of its testing cycle and there should be a new
release available soon that may address the problem.
In the mean time you can report problem web sites (that use up memory or
cause the browser to crash or which don’t render properly in any of IE8's
rendering modes) with the Web Page Problems report tool. Download from -
http://www.microsoft.com/downloads/t...displayLang=en
If you can identify which sites may be causing this and post them back here,
it would be most helpful.
Note also, that you should also test IE8 in no-Addons mode to eliminate
effects caused by Addons.
Regards.
"bob" <bob@discussions.microsoft.com> wrote in message
news:FFA3F8DA-AE13-476C-AEB1-DBB896F2F3DF@microsoft.com...
> i use win xp pro, with a 2.2g processor and 1gb memory and ie7
> i usually have 3-6 instances of ie7 going, trying to multitask and just
> like
> the convenience of having some windows open that might refresh on their
> own,
> eg. yahoo finance, and searching down something where i want to keep the
> trail.
> at some point ie7 will start to gobble up cpu usage to a point that it is
> causing 100% usage system wide. it maybe 50,60,70 itself and the other
> apps
> using a combined remainder of cpu and i pretty much start grinding to a
> halt.
> so i just kill ie in task manager, system goes back to a high % of system
> idle, and i start all over again. ususally it seems to be one instance of
> ie
> that causes the problem. i can exit each instance separately and get the
> same
> result. but its just quicker to go to task manager and do it all at once.
> is
> there some settings that can give better behavior?
> i dont remember having this same problem with ie6. don't have the same
> problem with firefox, so it seems its unique to ie7.