ie7 sticks windows after closing

IE7 "sticks to Windows" after closing

Hmm... there really should be an IE7 newsgroup...
One thing I've noticed in IE7 for XP SP2, is that once I close down Internet Explorer 7, I can leave my machine for about 10 minutes say, and check Task Manager (I do this once in a while just to check how memory is) and most of the time, I'd say 90% of the time the process "iexplore.exe" is still there.
Sometimes it's reached up to 100,000K as the Memory Usage, and the overall pagefile usage can be as high as 400MB on my 512MB laptop. The only way to really close IE7 down is to kill it from the Task Manager. Has anyone else noticed this or does this just happen on every machine I touch? Hehe.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

This also happens in Internet Explorer 6 on XP SP2. It looks like it has not fixed in Vista. What I do is not rush the computer to shutdown, give it sometime to at least come out of memory. I remember a post about Internet Explorer 7 issues from the public must be discussed in the web based version of Internet Explorer newsgroups, its just not available in Outlook Express, but it should be. -- -- Andre Windows Connect | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"Zack Whittaker (R2 Mentor)" wrote in message

Hmm... there really should be an IE7 newsgroup...
One thing I've noticed in IE7 for XP SP2, is that once I close down Internet Explorer 7, I can leave my machine for about 10 minutes say, and check Task Manager (I do this once in a while just to check how memory is) and most of the time, I'd say 90% of the time the process "iexplore.exe" is still there.
Sometimes it's reached up to 100,000K as the Memory Usage, and the overall pagefile usage can be as high as 400MB on my 512MB laptop. The only way to really close IE7 down is to kill it from the Task Manager. Has anyone else noticed this or does this just happen on every machine I touch? Hehe.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Andre Da Costa [Extended64] wrote:

This also happens in Internet Explorer 6 on XP SP2. It looks like it has not fixed in Vista. What I do is not rush the computer to shutdown, give it sometime to at least come out of memory. I remember a post about Internet Explorer 7 issues from the public must be discussed in the web based version of Internet Explorer newsgroups, its just not available in Outlook Express, but it should be.

It also happens on FireFox 1.5

I haven't had any problems with IE6 on XP SP2, but Firefox does sometimes remain in Task Manager after closing it. Haven't had any issues with it eating memory though.
No problems now with either IE6 or Firefox in XP x64.

You see I never noticed it on IE6 on XP SP2 but certainly know about it now. Is it going to be some kind of system process that stays there so you can load up IE7... even faster, or is this a bug which is going to be fixed pretty soon?
Also I wish they'd disable the "auto focus" window thing - sometimes I open up a link in a new window and go back to the old one to continue looking... and suddenly the new page will popup to focus. That really grinds my gears that!!
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!
--- Original message follows --- "Jane Colman" wrote in message

I haven't had any problems with IE6 on XP SP2, but Firefox does sometimes remain in Task Manager after closing it. Haven't had any issues with it eating memory though.
No problems now with either IE6 or Firefox in XP x64.

"Zack Whittaker (R2 Mentor)" wrote in message news:%23n4J56hRGHA.1096@TK2MSFTNGP11.phx.gbl

Hmm... there really should be an IE7 newsgroup...
One thing I've noticed in IE7 for XP SP2, is that once I close down Internet Explorer 7, I can leave my machine for about 10 minutes say, and check Task Manager (I do this once in a while just to check how memory is) and most of the time, I'd say 90% of the time the process "iexplore.exe" is still there. Sometimes it's reached up to 100,000K as the Memory Usage, and the overall pagefile usage can be as high as 400MB on my 512MB laptop. The only way to really close IE7 down is to kill it from the Task Manager. Has anyone else noticed this or does this just happen on every machine I touch? Hehe.

Windows keeps as much as it can of your last closed program(s) as possible so that if you want to open it again it opens faster.
--
Frank Saunders, MS-MVP OE Please respond in Newsgroup. Do not send email http://www.fjsmjs.com Protect your PC http://www.microsoft.com/security/protect/

mmmm, isn't this up to the developer of that program?
or when you say, windows does this, do you mean programs written by MS.
If windows kept exe your program running after it received a WM_QUIT message and then when you restart your EXE, does window, send a WM_DONTQUIT? this message does not exist.
Steve
"Frank Saunders, MS-MVP OE" wrote in message

"Zack Whittaker (R2 Mentor)" wrote in message news:%23n4J56hRGHA.1096@TK2MSFTNGP11.phx.gbl Hmm... there really should be an IE7 newsgroup...
One thing I've noticed in IE7 for XP SP2, is that once I close down Internet Explorer 7, I can leave my machine for about 10 minutes say, and check Task Manager (I do this once in a while just to check how memory is) and most of the time, I'd say 90% of the time the process "iexplore.exe" is still there. Sometimes it's reached up to 100,000K as the Memory Usage, and the overall pagefile usage can be as high as 400MB on my 512MB laptop. The only way to really close IE7 down is to kill it from the Task Manager. Has anyone else noticed this or does this just happen on every machine I touch? Hehe.
Windows keeps as much as it can of your last closed program(s) as possible so that if you want to open it again it opens faster.
-- Frank Saunders, MS-MVP OE Please respond in Newsgroup. Do not send email http://www.fjsmjs.com Protect your PC http://www.microsoft.com/security/protect/

"Steve Drake" wrote in message news:735AE31D-7D7E-4247-94B3-E7FB17D2291E@microsoft.com

mmmm, isn't this up to the developer of that program?
or when you say, windows does this, do you mean programs written by MS. If windows kept exe your program running after it received a WM_QUIT message and then when you restart your EXE, does window, send a WM_DONTQUIT? this message does not exist.

The programmer is responsible for releasing memory the program's data. Windows keeps the program code "just in case". Have you never noticed that programs load much faster right after they've been closed? As soon as another program needs the memory it is available.
-- Frank Saunders, MS-MVP OE Please respond in Newsgroup. Do not send email http://www.fjsmjs.com Protect your PC http://www.microsoft.com/security/protect/

That's disk caching and... any resource that the program use are also cached.
But.... the process will not still be listed in task manager, that's what this thread started as :) hence my reply :)
Some program can be written in such away that they 'in simple terms' just hide, then hang around, just incase the user didn't mean to quit, they normally lock onto a mutex, when the program gets loaded again, it checks for the mutex, if its locked, it will know that it has a copy hanging around and it will tell the 'hanging' around program to un hide itself.
Outlook did this (or at least it did something like this with the old mapi spooler), not sure if it still does, I am running beta OS and BETA office, so it would not be a good test on my PC.
Thanks
Steve
"Frank Saunders, MS-MVP OE" wrote in message

"Steve Drake" wrote in message news:735AE31D-7D7E-4247-94B3-E7FB17D2291E@microsoft.com mmmm, isn't this up to the developer of that program?
or when you say, windows does this, do you mean programs written by MS. If windows kept exe your program running after it received a WM_QUIT message and then when you restart your EXE, does window, send a WM_DONTQUIT? this message does not exist. The programmer is responsible for releasing memory the program's data. Windows keeps the program code "just in case". Have you never noticed that programs load much faster right after they've been closed? As soon as another program needs the memory it is available.
-- Frank Saunders, MS-MVP OE Please respond in Newsgroup. Do not send email http://www.fjsmjs.com Protect your PC http://www.microsoft.com/security/protect/

Windows Vista

Topic:


Nick: