iexplore.exe: Memory usage climbs, then holds static, after closing

Forum Moderators: open

Message Too Old, No Replies

iexplore.exe: Memory usage climbs, then holds static, after closing

O/S or WinExpl not releasing memory after tabs closed? Fix?

Webwork

3:36 pm on Mar 26, 2007 (gmt 0)

I'm runing Windows XPPro and the Windows Explorer 7.0

As I open additional tabs memory useage keeps climbing - as expected - but there appears to be a system quirk whereby the memory usage remains nailed at or near the highest CPU usaage number even after I have closed all the additiontal tabs. It's as if there's a programming glitch, whereby CPU/memory isn't released after closing the added tabs.

This results in my PC slowing down noticeably next time I open a new tab or two, whereas on the first time I'm opening tabs I can open about 10 without noticing a slowdown.

Anyone have a fix for this? Other than closing down Windows Explorer completely and restarting Explorer from scratch?

Fix /= (not equal to) 'use FireFox'. :)

bill

12:18 am on Mar 27, 2007 (gmt 0)

Use Opera ;)

Microsoft has a HotFix for an IE7 memory issue:

Memory usage increases in the Iexplore.exe process when you refresh a Web page that contains XML content in Internet Explorer 7 [support.microsoft.com]

Could that be it?

milanmk

8:11 am on Mar 27, 2007 (gmt 0)

I too have the exact problem with IE6 on WinXP Pro SP2. I even tried installing the latest updates for IE6 but that too did not helped.

Milan

Webwork

10:30 pm on Mar 27, 2007 (gmt 0)

Thanks for the tip Bill. I'll investigate further.

Not sure it's an XML issue unless almost all websites are 'part of the problem' since I suffer the slowdown pretty consistently, i.e., it appears that all websites contribute to the rising binding of CPU. Once I visit any site, even after I close the tab for that site, the CPU usage remains elevated and keeps rising as I open and close tabs.

Interesting. I'll follow up on the tip this weekend and report back if this fixes the problem. Thanks again.

P.S. Having now read the article linked above it certain describes what I've been experiencing. Anyone have an idea about how one would determine if the pages being viewed are "as described in the article"? How do I know if the page issue IS XML based? (Not essential that I know but if there's a quick answer that would be interesting.)

[edited by: Webwork at 10:35 pm (utc) on Mar. 27, 2007]