Perhaps, but without asking the IE team or debugging the internal structures of each process, we can't really be sure one way or the other. Could even be a combination of all of them.
I suppose one of the MVPs based in NA could jump on the next IE MVP team chat - they are usually quite helpful in explaining how things work in IE. I usually can't be bothered because of the time zone differences between here and Seattle. Cheers Ken From: Carl Houseman [mailto:[email protected]] Sent: Friday, 20 March 2009 12:33 PM To: NT System Admin Issues Subject: RE: IE8 vs. IE7 memory consumption I'd say the difference is the duplication overhead for running 9 iexplore.exe processes vs. 1 process. Carl From: Ken Schaefer [mailto:[email protected]] Sent: Thursday, March 19, 2009 9:13 PM To: NT System Admin Issues Subject: RE: IE8 vs. IE7 memory consumption Is part of that memory usage cache though? If there's more aggressive in-memory caching of objects, script engines etc, then memory usage would increase, but only until Windows signalled a low-memory condition Cheers Ken From: Carl Houseman [mailto:[email protected]] Sent: Friday, 20 March 2009 9:16 AM To: NT System Admin Issues Subject: IE8 vs. IE7 memory consumption FYI, on Vista SP1 32-bit with 3GB and the same 18 tabs opened immediately after IE startup. IE7 (1 iexplore.exe process) Memory (PWS): 174MB Commit: 207MB IE8 (9 iexplore.exe processes) Memory (PWS): 273MB Commit: 436MB I know plenty of XP machines still at 512MB. Fortunately most of those users don't even know that multiple tabs are possible, pretty much work in one website at a time all day. Carl ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
