J
Jeff Loftus
Posted a few months ago by Francis Gerard here:
http://groups.google.com/groups?hl=...plorer+high+priority&btnG=Google+Search&meta=
I've written an MFC app to address this, as to date no Microsoft
updates have modified this buggy behavior. This app sits in the
System Notification area (sometimes erroneously referred to as the
"system tray") and periodically looks for high-priority instances of
explorer.exe and zaps them back to normal priority. There's a
"disable" context menu item, and the polling interval is configurable.
It's a small footprint and lightweight resource-wise.
If you'd like a zip of the project (Dev Studio 6) email me:
JeffLoftus-at-hotmail-dot-com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Francis' message here for convenience:
PROBLEM
- launch Windows Explorer
- from the Tools menu, select Folder Options
- select View tab
- check the box 'Launch folder windows in a separate
process'
- press OK
subsequent launches of Windows Explorer (explorer.exe)
will run at a 'High' base priority level.
this occasionally will cause other programs and sytem
activities to intermittently stall and/or become
unresponsive when using Windows Explorer, particularly
when viewing the contents of a folder that contains
multimedia files (mpg, avi, mp3) and pictures (jpg, gif)
RESOLUTION (temporary)
- launch Windows Task Manager
- locate the explorer.exe process running at High priority
- right-click on the process, select Set Priority, Normal
- press the Yes button on the Task Manager Warning dialog
subsequent (child) iterations of Windows Explorer will
launch within the parent explorer.exe process, and at
Normal priority level
however, if all folder windows are closed (not the desktop
explorer process), the problem re-occurs the next time
Windows Explorer is launched again
i consider this to be a serious bug because programs that
are time critical, such as audio/video software (Windows
Media Player, Movie Maker, Vegas Video, etc) will
temporarily stall because they are running at Normal
priority level when explorer.exe (running at High
priority) is launched and/or accessing folders/files in
Windows Explorer.
i prefer to have folder windows launch in a separate
process because it keeps the desktop process separate,
more responsive and less likely to crash/restart if
something goes wrong in a folder window. there is a large
(1GB) amount of RAM in my machine, so it is preferable to
run separate instances of explorer.exe for that reason as
well.
is this a known bug? i can't seem to find references to
it anywhere.
http://groups.google.com/groups?hl=...plorer+high+priority&btnG=Google+Search&meta=
I've written an MFC app to address this, as to date no Microsoft
updates have modified this buggy behavior. This app sits in the
System Notification area (sometimes erroneously referred to as the
"system tray") and periodically looks for high-priority instances of
explorer.exe and zaps them back to normal priority. There's a
"disable" context menu item, and the polling interval is configurable.
It's a small footprint and lightweight resource-wise.
If you'd like a zip of the project (Dev Studio 6) email me:
JeffLoftus-at-hotmail-dot-com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Francis' message here for convenience:
PROBLEM
- launch Windows Explorer
- from the Tools menu, select Folder Options
- select View tab
- check the box 'Launch folder windows in a separate
process'
- press OK
subsequent launches of Windows Explorer (explorer.exe)
will run at a 'High' base priority level.
this occasionally will cause other programs and sytem
activities to intermittently stall and/or become
unresponsive when using Windows Explorer, particularly
when viewing the contents of a folder that contains
multimedia files (mpg, avi, mp3) and pictures (jpg, gif)
RESOLUTION (temporary)
- launch Windows Task Manager
- locate the explorer.exe process running at High priority
- right-click on the process, select Set Priority, Normal
- press the Yes button on the Task Manager Warning dialog
subsequent (child) iterations of Windows Explorer will
launch within the parent explorer.exe process, and at
Normal priority level
however, if all folder windows are closed (not the desktop
explorer process), the problem re-occurs the next time
Windows Explorer is launched again
i consider this to be a serious bug because programs that
are time critical, such as audio/video software (Windows
Media Player, Movie Maker, Vegas Video, etc) will
temporarily stall because they are running at Normal
priority level when explorer.exe (running at High
priority) is launched and/or accessing folders/files in
Windows Explorer.
i prefer to have folder windows launch in a separate
process because it keeps the desktop process separate,
more responsive and less likely to crash/restart if
something goes wrong in a folder window. there is a large
(1GB) amount of RAM in my machine, so it is preferable to
run separate instances of explorer.exe for that reason as
well.
is this a known bug? i can't seem to find references to
it anywhere.