|
|
#1 |
|
Junior Member
Join Date: Mar 2001
Posts: 2
|
Winamp taking over CPU on close
Hey, I have a slightly wierd problem that has just developed since I installed Windows XP. Anytime I open Winamp (any amount of time) and then close it out, it then boosts my CPU usage up to 100% until I go into the task manager and end the process. I have a SB Live! and I've already removed gen_nomad.dll, all the MS patches have been installed, Norton AV 2002 disabled (to no avail), I've even tried removing/reinstalling Winamp but no success. Any ideas?
|
|
|
|
|
|
#2 |
|
Techorator
Winamp & Shoutcast Team Join Date: Jun 2000
Posts: 35,894
|
Installed any other third party plugins?
eg. gen_mircex or some lyrics plugin, or any WT games, etc? The Official 3rd-party Plugin Buglist RE: How do I remove 3rd-party plug-ins http://forums.winamp.com/showthread.php?threadid=26872 http://forums.winamp.com/showthread.php?threadid=26610 Troubleshooter Guides: http://forums.winamp.com/showthread....827#post275827 http://forums.winamp.com/showthread....166#post308166 Basic Uninstall -> Reinstall procedure: http://forums.winamp.com/showthread.php?threadid=50818 |
|
|
|
|
|
#3 |
|
Major Dude
|
I've been searching for threads that might have something to do with this. I just installed XP Pro over the weekend. I noticed that everytime I close Winamp, CPU usage rises to 100% for winamp.exe as it appears in the Task Manager, even though I had already exited Winamp. On top of that, once I've closed Winamp, I cannot open Winamp again, probably because it's still resident in Task Manager. And on multiple instances, and closing all those multiple instances, the CPU is pooled to 100%. The only way I can reopen Winamp is by ending the process in Task Manager manually, and that gets annoying.
I also don't have any of the buggy third-party plug-ins. I've also taken some screenies to prove my case: Before (with Winamp running) After (exit Winamp) (And yes, I'll be dropping AOL in a couple of weeks, leave me alone). I suppose I can just leave Winamp on till I shut down, but it still bugs me to no end. |
|
|
|
|
|
#4 |
|
Major Dude
|
I have also tried replicating this by doing a clean install with the last few versions of Winamp (2.78-2.80) and I get this too. This can be replicated by simply opening Winamp, and then closing it right after. I'm figuring it could be a problem with Winamp 2.x itself.
|
|
|
|
|
|
#5 |
|
Techorator
Winamp & Shoutcast Team Join Date: Jun 2000
Posts: 35,894
|
Your "before" & "after" images are the same.
Can we see the real "after" image, and also post a full list of all concurrently running programs/processes. I see you've got RealPlayer running, and CTHelper suggests you're using the shabby new Creative SB drivers . . . all relevant sys specs would help too. I can't reproduce the problem, then again I'm not using WinXP... though I'm sure there's plenty of WinXP/Winamp users out there who don't experience this problem, otherwise there'd be more than one report! Are you using ANY 3rd-party plugins? (not necessarily just the ones mentioned in the official bug list) Installed latest wa2update? Using WaveOut or DirectSound? Made sure correct device is set in Output config? |
|
|
|
|
|
#6 |
|
Major Dude
|
Hmm... well, I think I might have solved it. And you're right, it must have been some other plug-in that isn't on the list. I think I'll go back and find out which one it is.
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|