H
Hank Scorpio
Version 5.1.2600 Service Pack 2, Build 2600
This question has been asked before, but no-one seems to have had an
answer to it. I'm wondering whether (and hoping that) that has
changed.
I've noticed an increasing tendency for processes to be "unkillable".
Under an Admin login, you:
- Go to Task Manager,
- Find the process that has gone feral,
- Click on [End Process],
- Get the dialog that tells you "WARNING: Terminating a process can
cause undesired results",
- Click on the [Yes] button (MS please note; the correct caption for
that button should be [I'm running this machine, not you, just do what
I bloody tell you to do]) and...
- nothing happens. The process just keeps ticking away merrily,
completely ignoring you.
Naturally this interferes with any other instance of the process that
you may try to launch. For example, because you can't kill a zombie
WinWord.exe process, any attempt to reply to an Outlook message and
Outlook will hang as well since it tries to open a session of Word as
the message editor. Have enough applications go south on you (and the
gods know Office 2003 is really, REALLY good at going south on you),
and you end up with a system so unusable that a reboot is the only
remaining option.
(Word 2003 is exceptional at doing this if you forget about the woeful
piece of design which causes it to lock up if you copy something from
a web site and try to paste it into Word. Apparently this is a "really
awesome" piece of Web integration (everything needs to be Web
integrated, doncha know) where instead of just copying the data to and
from the clipboard, Internet Explorer and Word apparently decide that
the latter should try to get to the web site itself and pull down a
bunch of data, thus hanging itself. You can't kill the hung
WinWord.exe process, so you get the results described above. Second
memo to MS: This is what I pay the Clipboard for. It's not Word's job
to grab metadata from a Web site. It's Word's job to just paste the
clipboard data into the document, FROM the clipboard. And it would be
really nice if I could view the pasted pictures without having to turn
my graphics acceleration All-The-Way-Down half the time, but I
digress.)
Until tonight it's only been a problem with Office apps, but tonight
Acrobat Reader got in on the act. I found multiple processes (none
with a visible interface) and was able to kill all but one. That one
prevented me from launching Acrobat again.This is REALLY getting
annoying.
Does anyone have an idea of why this is happening?
This question has been asked before, but no-one seems to have had an
answer to it. I'm wondering whether (and hoping that) that has
changed.
I've noticed an increasing tendency for processes to be "unkillable".
Under an Admin login, you:
- Go to Task Manager,
- Find the process that has gone feral,
- Click on [End Process],
- Get the dialog that tells you "WARNING: Terminating a process can
cause undesired results",
- Click on the [Yes] button (MS please note; the correct caption for
that button should be [I'm running this machine, not you, just do what
I bloody tell you to do]) and...
- nothing happens. The process just keeps ticking away merrily,
completely ignoring you.
Naturally this interferes with any other instance of the process that
you may try to launch. For example, because you can't kill a zombie
WinWord.exe process, any attempt to reply to an Outlook message and
Outlook will hang as well since it tries to open a session of Word as
the message editor. Have enough applications go south on you (and the
gods know Office 2003 is really, REALLY good at going south on you),
and you end up with a system so unusable that a reboot is the only
remaining option.
(Word 2003 is exceptional at doing this if you forget about the woeful
piece of design which causes it to lock up if you copy something from
a web site and try to paste it into Word. Apparently this is a "really
awesome" piece of Web integration (everything needs to be Web
integrated, doncha know) where instead of just copying the data to and
from the clipboard, Internet Explorer and Word apparently decide that
the latter should try to get to the web site itself and pull down a
bunch of data, thus hanging itself. You can't kill the hung
WinWord.exe process, so you get the results described above. Second
memo to MS: This is what I pay the Clipboard for. It's not Word's job
to grab metadata from a Web site. It's Word's job to just paste the
clipboard data into the document, FROM the clipboard. And it would be
really nice if I could view the pasted pictures without having to turn
my graphics acceleration All-The-Way-Down half the time, but I
digress.)
Until tonight it's only been a problem with Office apps, but tonight
Acrobat Reader got in on the act. I found multiple processes (none
with a visible interface) and was able to kill all but one. That one
prevented me from launching Acrobat again.This is REALLY getting
annoying.
Does anyone have an idea of why this is happening?