Re: Memory/Resource leak continues w/ IE 6, WinXP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi Bram,

First up disable all your browser helpers (Internet Options - Advanced tab,
uncheck "Enable third-party browser extensions")

Restart IE.

If the problem persists, open Task Manager (Ctrl+Alt+Del) and on the
Processes tab sort them by CPU (click on the column title) to find which
process is hogging the CPU. If it is IExplore.exe then my suggestion (well
you should do this regardless, WinXP SP1 is a bit out of date!) is to do a
Windows update and get SP2 installed on your machine. This is quite a big
download so be prepared.

If disabling your browser helpers works then the problem lies with one of
your add-on toolbars. The Live toolbar (previously the MSN search toolbar)
is a known memory hog (on occasions), but you can test to find the culpret
by
1. Re-enable you browser extensions.
2. Restart IE and then disable the add-on toolbars one by one (Tools>Manage
Addons) until you find the culpret toolbar.

Above all keep your PC up-to-date with regular Windows Updates!

Regards.
"Bram Weiser" <BramWeiser@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8B2F6DA6-9E27-4750-BA30-AD708B32EC7F@xxxxxxxxxxxxxxxx
Hello, again, Everyone,

(My apologies if this seems a bit familiar to some of you, as I'd
previously
posted about this here, when I suspected that this issue was somehow
related
to Google or Yahoo! toolbars, but, even though they're both uninstalled
from
my PC, this issue has appeared again, so may I please ask for your
assistance?)

For reasons that escape me, my IE 6 browser can open up its regular
complement of windows in WinXP SP1 BUT, after reaching their limit, once I
then start to close some of them, I become unusually limited as to how
many I
can open afterward.

Usually, it's supposed to be fairly one-to-one (close one, become able to
open another one) but, now, it's more like close two, maybe open one...if
you're good. ;)

No, seriously, something's amiss here. This isn't supposed to happen, and
it's like not enough memory or resources are being returned to the system
after closing a window.

BTW, if I shut down all IE windows that remain open, I can then go
back...for a time...to opening the full complement of windows again, and
I'm
back where I started.

Can you please guide/assist me to try and resolve this? Any questions,
please ask and I'll be happy to answer the best I can.

Thanks so much!

Bram


.



Relevant Pages

  • Re: networking xp with 98SE issue
    ... I'll bet you have a browser problem here (I'm not talking about Internet ... The Windows 98 and Windows XP browsers don't work well on the same ... browser on the Windows 98 browser computers, and disable it on the other Windows ... After checking / disabling / enabling as above, power all computers off to reset ...
    (microsoft.public.windowsxp.network_web)
  • Re: Internet Connection Sharing AND networking?
    ... >> browser problem. ... >> situation with Windows 98 and Windows XP on the same LAN. ... I still can't see the XP Pro machine ... after disabling the browser on the 98 computer? ...
    (microsoft.public.windowsxp.network_web)
  • Re: Windows 98 Server and XP pro SP2
    ... Check for a browser conflict between the WinXP computers and the Win98 ... the server running Windows 98, you should use the Windows 98 server, and one ... After checking / disabling / enabling as above, power all computers off to reset ...
    (microsoft.public.windowsxp.network_web)
  • Re: Cant see other PCs on LAN
    ... >I'm trying to see the other computer I'm using Windows Explorer. ... Check for a browser conflict between the two computers. ... After checking / disabling / enabling as above, power all computers off to reset ... The Microsoft Browstat program will show us what browsers (I'm not talking about ...
    (microsoft.public.windowsxp.network_web)
  • Re: XP Service Pack 3
    ... IE7 is not a browser update. ... the versions on Windows Vista and also on Windows XP SP2. ... > Internet Explorer is already outdated, ...
    (microsoft.public.windowsxp.general)