FIXED: 100% cpu with winamp

[dragonfang]

winamp (v 2.91) is responsible for 100% cpu under the condition that windows is locked (whether by screensaver or by winkey+L) 100%usage still occurs when the welcome screen and fastuserswitch is disabled.
winamp operates perfectly normal with the exception of the screensaver conflict.
it's annoying to have your temps go up just because winamp doesnt like windows locked

yes, it even does this when winamp is not playing any songs. i havent been able to find any info on this. i'd appreciate feedback

thanks

using winxp sp1 btw

 

[Alienwho]

I've also had this problem on numerous and random occasions. I can't seem to reproduce it when I want, but it just happens randomly every now and then.

 

[dragonfang]

yea this error is reproducable everytime

 

[secretanchitman]

had this happen to me before...i upgraded to sp2 and the problem went away.

any reason not to upgrade to sp2? actually...there isnt any reason to upgrade, and i still installed it.

 

[dragonfang]

i don't feel there's any need to go sp2. i've heard bad stories about it

 

[otispunkmeyer]

Originally posted by: dragonfang
i don't feel there's any need to go sp2. i've heard bad stories about it

SP2 here since it came out.....no problems, ever.

 

[Megatomic]

Originally posted by: dragonfang
i don't feel there's any need to go sp2. i've heard bad stories about it

It's fine if your windows is legit.

 

[dragonfang]

this thread wasnt meant to debate sp2 ty.

 

[Powermoloch]

Originally posted by: Megatomic

Originally posted by: dragonfang
i don't feel there's any need to go sp2. i've heard bad stories about it

It's fine if your windows is legit.

I got sp2...and the only difference that came with it is added security thingamijig and active x?

lol

At least windows updater wont bother me forever

 

[Injury]

Originally posted by: dragonfang
this thread wasnt meant to debate sp2 ty.

But it was posted as a possible fix to your problem, so I really can't think of any reason you wouldn't at least try this unless you don't have a legit cop of windows, in which case, I hope your problem is not fixed at any time.

 

[gorcorps]

Originally posted by: dragonfang
this thread wasnt meant to debate sp2 ty.

This isn't a sp2 debate... it's reasons why you shouldn't be afraid to upgrade. You have your solution, it's up to you now what to do from here. You're pretty snippy at the people trying to help here.

 

[secretanchitman]

have you tried uninstalling and reinstalling winamp? how about going to winamp5 (not that bloated if you uncheck all the crap)?

 

[dragonfang]

Originally posted by: gorcorps
This isn't a sp2 debate... it's reasons why you shouldn't be afraid to upgrade. You have your solution, it's up to you now what to do from here. You're pretty snippy at the people trying to help here.

suggesting to upgrade to sp2 for a minor problem such as this is very impractical and a tad drastic (and a lazy attempt at a suggestion). a solution would fix a problem. so no, i don't have a solution, only a time-consuming suggestion. i appreciate it, but it'd be more helpful if we can stop fixating on sp2. it feels like i'm being surrounded by a cult of sp2 evangelists. sp1 has never given me a problem and i doubt that this winamp problem is caused by sp1 (or that it can be solved by upgrading to sp2). and also if sp2 did solve the problem, it would be a workaround, not a fix.

btw i have a legal copy of windows. but contrary to popular belief, an illegal copy of windows (available on almost every bt site) would work just as well as a legal copy. i dont see how it would affect normal operation.

Originally posted by: secretanchitman
have you tried uninstalling and reinstalling winamp? how about going to winamp5 (not that bloated if you uncheck all the crap)?

i just tried winamp5. strangely, it didnt give me 100%usage. thanks, you've narrowed it down to a version issue. im still curious as to why it would do that on 2.91 though. i would still like to use my old winamp. any ideas?

 

[Injury]

Originally posted by: dragonfang
suggesting to upgrade to sp2 for a minor problem such as this is very impractical and a tad drastic (and a lazy attempt at a suggestion). a solution would fix a problem. so no, i don't have a solution, only a time-consuming suggestion. i appreciate it, but it'd be more helpful if we can stop fixating on sp2. it feels like i'm being surrounded by a cult of sp2 evangelists. sp1 has never given me a problem and i doubt that this winamp problem is caused by sp1 (or that it can be solved by upgrading to sp2). and also if sp2 did solve the problem, it would be a workaround, not a fix.

... except that the problem could be a bug directly caused by windows that was fixed with SP2 files.
Back in the days of Counter-Strike 1.1, I was having random crashes that nobody on the CS forums knew would fix it. Turned out that I needed to update my directX drivers or some crap. Just because a program is running when something is wrong doesn't mean it's directly that program that causes something.

 

[dragonfang]

Originally posted by: Injury

... except that the problem could be a bug directly caused by windows that was fixed with SP2 files.

Just because a program is running when something is wrong doesn't mean it's directly that program that causes something.

yes i know that sp2 could potentially fix the problem (and once again i point out that it would be a workaround, not a fix). i grasped your point the first time you said it. you don't have to tell me the obvious. what i keep saying is how impractical it would be to upgrade to sp2. it's probable that sp2 would fix the problem but the impracticality of it all outweighs the problem. so please, no more sp2 stories.

i found a list of known issues according to versions here
http://forums.winamp.com/showthread.php?threadid=51934
i skimmed through it without any luck. when i previously said i tested with winamp5, i was using 5.01. i might try installing an earlier version than 2.91 to see if it's a winamp2 problem.

edit:
ok. i tried v2.90 and also tried a fresh install of v2.91 where the 100% usage didn't appear. it's definitely a problem with my current install. im going to play around with the settings and plugins to see what turns up.

 

[dragonfang]

ive finally found the problem.

i started off by creating another copy of the winamp2 folder for diagnostic purposes. i started by deleting each folder, starting winamp, undeleting it if it still gave 100%usage. the problem stopped with the plugin folder. once it was narrowed down to plugins i went through the same process of deleting and undeleting for each category (in,out,viz,gen). it turns out that the culprit (i have to mention that i have tons of plugins installed most of which i never use) was lucidamp3.5
i never used this plugin (it wasn't even active when i checked the settings before uninstalling) and i shouldve uninstalled it on that same day i installed it. uninstalled it, no more 100%usage. solution found. thanks to secretanchitman who first suggested winamp5. it eventually led me to plugin inspection

the moral of all of this? uninstall any plugins you dont need.

and fyi, sp1 is a perfectly stable setup. ive never felt the need to "upgrade" to sp2.

 

[erikistired]

yarrrrr.

 

[nweaver]

lmao....


"Guys, Word Perfect 3.1 is crashing on my Dos 5.0 box..and don't tell me to update anything!"