|
2002 03 13 Wednesday dyree(e) in K
| winamp on NT: CPU hog after suspend |
 | Listening to an audio CD, put laptop running WinNT 4.0 sp6 into suspend; upon resume, winamp grabs 99% of CPU according to task manager. the only alternative to a brutal power off is to call up the task manager and kill the winamp process. Since even the task manager igetting only a fraction of 1% of the CPU, this takes approx 10 - 15 minutes, during which you have to stay glued to the screen, waiting for |
| the list of procs to display |
| the right-click on the winamp proc to pop a context menu |
| the context menu to display |
| the "end process" entry to activate |
| your click on it to be accepted |
| the Task Manager Warning about terminating processes to pop up |
| to display fully |
| to accept your click on ok |
| the task manager to regain focus |
| to redisplay all processes, one by one |
| and eventually, the winamp process to die, everything returning to normal |
| I think there is some serious problem with an OS that allows a user process to grab so much CPU as to disable the core OS functions. All the same, maybe there is something Winamp developers can to in this case? |
| suddenly, over the past two hours, i'm in a bad mood. is it |
| the dentist hit a nerve? |
| C asked me to accompany him to CeBit and i declined, but feel bad about damping his enthusiasm? |
| or is it that i am using MS Word for the first time in a long while? |
|
.
.
.
.
.
home
.
english
.
deutsch
.
siteindex
.
.
.
.
.
.
.
.
.
.
.
.
.
.
|