Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Build 7229 x64 Explorer.exe memory issue

28 Jun 2009   #1
pillainp

Windows 8.1 Professional 64-Bit
 
 
Build 7229 x64 Explorer.exe memory issue

As you can see from my system specs, I am running Windows 7 Build 7229 x64, and am having no major issues so far.

There is one little niggle that I have noticed, though:

With Explorer set to open windows in separate processes, a new process is opened whenever a new explorer window is opened (as expected).

However, as you can see from the attached screenshot, the individual processes for the multiple instances of explorer.exe are not terminated once the instances are closed. The persist as running processes and the only way to reclaim the RAM is to kill them manually.

However, when the "separate processes" option is turned off (ie All explorer windows open within a single process), the original process consumes more and more RAM as each new instance is opened. When all the instances are then closed, explorer still retains the RAM without releasing it, until the process is killed and restarted.

Is this a bug? If so, is there a solution?

This was more or less an accidental finding, since there is no appreciable effect on system performance when this happens.




Attached Images
Build 7229 x64 Explorer.exe memory issue-capture.png 
My System SpecsSystem Spec
.
28 Jun 2009   #2
masterB

Windows 7 Professional x64
 
 

You can install build 7232 and and it may fix the problem.
My System SpecsSystem Spec
28 Jun 2009   #3
fakeasdf

Win 7 Pro x64 x 3, Win 7 Pro x86, Ubuntu 9.04
 
 

Quote   Quote: Originally Posted by pillainp View Post
As you can see from my system specs, I am running Windows 7 Build 7229 x64, and am having no major issues so far.

There is one little niggle that I have noticed, though:

With Explorer set to open windows in separate processes, a new process is opened whenever a new explorer window is opened (as expected).

However, as you can see from the attached screenshot, the individual processes for the multiple instances of explorer.exe are not terminated once the instances are closed. The persist as running processes and the only way to reclaim the RAM is to kill them manually.

However, when the "separate processes" option is turned off (ie All explorer windows open within a single process), the original process consumes more and more RAM as each new instance is opened. When all the instances are then closed, explorer still retains the RAM without releasing it, until the process is killed and restarted.

Is this a bug? If so, is there a solution?

This was more or less an accidental finding, since there is no appreciable effect on system performance when this happens.
By launching windows in their own process I assume you are talking about the option in the view tab of folder options "Launch folder windows in a separate process." So if you are talking about something else then most of my response will be irrelevant.

I tested this on
7068 x86
7201 x64
7229 x64

Single Explorer:
On all three of them when the not using separate processes the memory on explorer didn't dump right away, but over time it did return down to a similar memory level. My guess is this has to do with their memory management and it not freeing memory right off the bat. But I did see that it didn't free it up instantly...

Multiple Explorer:
Now each time you open up an explorer window it doesn't open up a new Explorer process, but it will have 1 extra explorer process open that will handle folders specifically... And on all 3 builds I tested it would open when I opened my first window and subsequent windows would just increase the memory of that process. When all windows were closed it would hang around, but after a minute or two it would terminate.

Personal Opinion:
My guess is maybe your explorer is getting confused or locked and is unable to close properly, but it believes it is in a closing or closed state. Hence why you had so many explorer processes. And I'm not sure what could be causing this, my guess would be a virus scan software, or some other intrusive software that integrates itself into explorer. I don't know if you have anything like this, but you might check it out! Good Luck.
My System SpecsSystem Spec
.

28 Jun 2009   #4
copernicus

7264x64/7260x86
 
 

I just opened a slew of explorer windows after turning on that option and I'm only getting three seperate explorer processes.

?

But I'm on 7100 heh.
My System SpecsSystem Spec
Reply

 Build 7229 x64 Explorer.exe memory issue




Thread Tools




Similar help and support threads
Thread Forum
Explorer refresh x64 build 7229
I realsie this is a build that not many of us are still using, but I found the foolowing issue. When in explorer, if I right click on a file and then delete it, it remains in explorer until I manually refresh. Is this normal? very annoying. Mark
General Discussion
Windows 7 build 7229 PunkBuster
It has been just leaked (x86 & x64). Please can someone install it and test if PB works? If it does, I will move from 7201 to 7229 :D
Gaming
2 Probs with build 7229 (X-64)
Hi all I think something in 7229 has slipped the regression test 1) - already reported -- Acronis True Image Workstation fails (also a prob in build 7201 but OK in 7137) All x-64 builds. 2) Outlook 2007 with SP2 applied (Office Enterprise 2007) can't connect to an exchange server - new...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:16.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App