Re: explorer.exe loaded at high priority, often left in memory
From: fm (postmaster_at_127.0.0.1)
Date: 08/20/04
- Next message: Tim Slattery: "Re: Partitions"
- Previous message: bert: "Sp2 update solution"
- In reply to: Vanguardx: "explorer.exe loaded at high priority, often left in memory"
- Next in thread: Vanguardx: "Re: explorer.exe loaded at high priority, often left in memory"
- Reply: Vanguardx: "Re: explorer.exe loaded at high priority, often left in memory"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 20 Aug 2004 18:44:17 +0200
Vanguardx wrote:
> Most times, explorer.exe (Windows Explorer) runs at Normal priority.
> However, sometime later I will notice that it is running at High
> priority. This isn't the instance of explorer.exe used for the desktop
> GUI which always is at Normal priority. This is sometime later after
> opening and closing Explorer several times and I notice there is a
> second instance of explorer.exe hanging around after all Explorer
> windows have supposedly been closed. It's like Windows XP is caching an
> instance of explorer.exe because I've used it a lot. However, if I open
> Explorer and it is running at High priority then using it for something
> busy, like deleting thousands of files, results in the system getting
> slower. It is busy at High priority which takes away CPU time from
> everything else, including the desktop, that is running at Normal
> priority. It can get so busy at times that trying to get Task Manager
> up can be arduous (so I can drop the priority of this instance of
> explorer.exe back down to Normal).
>
> This loading of explorer.exe at High priority has never occurred under
> Windows 95, 98, 98SE, ME, NT4, and 2000. I've done the usual anti-virus
> and malware checks. Besides, I'll see in Task Manager an new instance
> of explorer.exe get loaded - and at High priority whether I use the
> Start menu shortcut or run explorer.exe using Start -> Run - when it is
> me that loads Explorer. I'll sometimes find a second instance of
> explorer.exe still loaded in memory when looking in Task Manager
> although all Explorer windows have been closed. It isn't busy (i.e., no
> CPU time). If it is loaded and I open Explorer, this second instance of
> explorer.exe gets reused; i.e., it isn't a remnant instance left behind
> from a hung exit of the program that is unresponsive as is a continued
> and known problem with Microsoft's outlook.exe and winword.exe
> processes.
>
> I really don't want a remnant yet responsive (i.e., unwindowed but
> reused) 2nd instance of explorer.exe left loaded in memory when I exit
> Explorer, and I don't want it loaded at High priority, either. When I
> exit Explorer, I'd like explorer.exe (the one not for the desktop) to
> get unloaded. When I load Explorer, I don't want it at High priority.
> I'll use Task Manager and use it to up the priority if and when I want
> (and right now I have to use it to *lower* the priority to Normal).
>
I do not know about your high-priority problem, but if you try to close
the last explorer.exe process in TaskMan, you will notice that explorer
is part of what makes Windows respond to your interaction with it...
- Next message: Tim Slattery: "Re: Partitions"
- Previous message: bert: "Sp2 update solution"
- In reply to: Vanguardx: "explorer.exe loaded at high priority, often left in memory"
- Next in thread: Vanguardx: "Re: explorer.exe loaded at high priority, often left in memory"
- Reply: Vanguardx: "Re: explorer.exe loaded at high priority, often left in memory"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
