5.32 - closing won't end winamp.exe process
 

i just installed 5.32 with modern skin support (on a winxp sp1 - no, i don't want sp2 - system that is working fine).

i mention modern skin support because i've never used that in the past. and also never seen this problem.

when i close winamp the winamp.exe process continues to exist in the 'Task Manager'.

if i attempt to start winamp again another winamp.exe process is created. but winamp will not appear for a minute of so (presumably because of something to do with the pre-existing winamp.exe process).

if i kill all winamp.exe processes and then start winamp all is well (winamp appears immediately without delay).

has anyone else ever witnessed this behavior?


-- david

i just did a clean install on another computer. and then installed winamp. same problem.

when i do a clean install i usually disable a number of services that are not needed. are there any services winamp 5.32 is dependent on that would prevent the winamp.exe process from ending when winamp is closed?


-- david

i'm getting closer to the source of the problem.

both machines had dx 8.1 installed. after upgrading the second machine to dx 9.0c the problem disappeared.

later on i will upgrade the first machine to dx 9.0c and see what happens. if the problem goes away then i recommend that the system requirements http://www.winamp.com/player/faq/index.php#30 be modified to include dx 9.0c.

ideally of course one of the winamp programmers will look into why winamp is having trouble closing when the direct x version is 8.1.


ciao,
david

well, i needed to uninstall and re-install winamp. and now the problem has reappeared. so i guess it's not necessarily a dx issue.

what a pita. i'm half ready to go back to winamp 3.91.


-- david

Have the same problem...
 

I' ve just downloded and installed winamp 5.11 to 5.32.
And this thing has comming up - winamp process doesn't terminate itself. I need kill it manualy through Task Manager.

Any idea how to solve this problem?

Please provide more info:
http://forums.winamp.com/showthread....d=161361#specs

I am having the same problem intermittently. Sometimes it won't play at all, I close and restart and there are two processes running for winamp. Today it played for one and a half minutes of music then froze completely... close... check task manager... still there... It was an mp3 in this case.

LG LS50 laptop
512MB Ram 1.6GHz Centrino
Windows XP SP2
Directx 9.0c
Winamp 5.32 Full Free
No plugins
Shared settings

HJT attached.

I'm having the exact same issue.

This in on a brand new install on a new computer
Core 2 Duo
2 GB RAM
Windows XP SP2
Version 5.32
No plugins
Free Version

Just a futher couple of symptoms if it helps anybody come up with any ideas...

When I restart or shutdown, windows has to manually shutdown winamp.exe again for every instance that I have attempted to reopen it i.e. if I have opened winamp 3 times after winamp has failed and killed the process four times in task manager, I still need to kill it four times on shutdown even though it is no longer visible in task manager...

And if winamp is merrily playing along nicely and freezes i.e. all tracks stop playing, cannot start playing again, cannot fast forward etc, all sound across my system is knocked out. WMP plays but does not produce sound, no mouse clicks in IE, no nothing.

The first thing I would suggest is if you are going to run up to date software, run the up to date operating system...

There are slight changes that are made.. in most software.. when the operating systems up date so do the software for that purpose..

If you use automatic up dates, and still have the issue I woudl then Open IE7 go to tools and then To Update, there your computer will be checked for its hardware, and software version and you will advised on what other downloads and possible options updates you can apply to bring the system completely up to date. These are not applied vis automatic updates as only Critical updates are notifies and applied automatically..

Also, make sure that you give the program time to initialize..
Big new computer well, it still may need a little time.. when yo have a good system sometimes you are like 'hurry up!' ya know and clicking off the mouse doesn't really help..

You can also make your screen size larger and see if its not just out of viewing range and also check your task bar to make sure its not starting up minimized..

If you are seeing winampa.exe running this is the icon which you will see also in your task bar and it is called WinAmp Agent which is used for shell integrating and maintaining file associations for the file you choose WinAmp to be the default program for..

If and after you update yo may want to grab the latest Winamp version 5.32 and its updates available in the forums about version 5.32

I am a user as well and have run into this before but I have 0 problems and I run completely up to date software and use protection from Windows Live One Care Beta 1.5..Without updates you are opening yourself up to several vulnerabilities...and eventually you will have to stay with versions of software which was good for that version and when that version was supported..Coordinating the time line

My advice...do what you will


You also may want to check your plug-ins as well and include a complete list of all of your plug-in as described in the STICKIES ...

there someone will pick up the thread who can give you other information

Thanks for the reply. Everything is up to date. I don't run winampagent. It's a computer that has run fine for some time (not new). And I don't have any plugins - all my info is posted further up the screen in my initial post.

Cheers

Hi,
a few things you could try...

Does this issue persist if you move ml_pmp.dll (Portable Media Player support) out of the Winamp plugins folder (C:\Program Files\Winamp\Plugins) while Winamp is closed?

If no luck, try disabling Sonic Ripping/Burning support by moving primosdk.DLL out of the Winamp root folder while Winamp is closed.

Also try these DirectSound output tweaks.

I just ran into this problem myself..it was after installing a few skins and a plug-in but I was also working on an avs presets compilation and had removed the contents of my avs folder...

When I did and I had winamp open..and opened windows explorer.. it screwed up the entire toolbar for my windows..I manged to fix the toolbar by redoing it and locking the toolbar .. then it extended downward and I could see no directory...

I tired to close winamp and the exe stayed open and the program would appear and disappear with th exe still open..

I could not figure out what it was.. Finally it woudl stay open and when I ran avs after testing my installer I noticed that avs presets where either inverted in color or flipped from reactive to non-reactive.. black and white ones where inverted as well..

I closed and installed a clean version in another folder and then tested the avs and program and it worked fine..

So I then put the contents of the avs folder back into place and it continued to work fine after that..


my problem was fixed.. I dunno I thought that was kinda related .. and kinda odd

I have exactly the same problem.

Well, did you try any of the suggestions in this thread? (e.g. the ones here)

Also, please do not crosspost (i.e. keep it to one thread).

Ok, this fixes my problem. But do i have an disadvantages by removing the file out of the folder?

By disabling ml_pmp.dll, you disable Portable Media Player support.

From the Winamp Component List:
By disabling ml_pmp.dll, all pmp_*.dll subplugins are also disabled.

It's probably one of the pmp_*.dll subplugins that causes the issue. If you need Portable Media Player support you could move ml_pmp.dll back into the Winamp plugins folder and figure out which of the subplugins is causing the issue (by moving them out of the plugins folder one by one).
At a guess, it's pmp_p4s.dll to blame. Though it's hard to say without extra info.

If you don't need to manage a portable via Winamp you can just leave ml_pmp.dll disabled.

seems to be pmp_activesync.dll

Guys, thank a LOT!
 

Actually, it helped me. I`ve just renamed "ml_pmp.dll" to "ml_pmp.dll.bak" then restart the winamp and after that it beginn to terminate itself normally again.

Strange thing that one of the default plug-in causes such fault.

Ditto
 

Same issue, same workaround

XPSP2 DirectX 9 dec 2006 Winamp Pro

Worked fine up 'till this latest 5.32, I usually accept the updates as they come, so assuming it was 5.31 that was fine.

I use the media player plugins so reluctant to move, rather just work around until the next update, so hopefully this bug is found and fixed.

you guessed right. i was just finishing up building another system (different from the one i originally posted about) and i ran into this problem again. as soon as i removed pmp_p4s.dll the problem ceased.

thanks for your help siebe83.

off-topic


this forum software or the way it is configured is a mite bit annoying.

two things:

since i can't edit my earlier posts i can't change a typo i made (when i referenced "winamp 3.91" i meant to type "winamp 2.91")

and what's up with the url that i included in one of my posts to this thread? it was simply a reference to a system requirements page on winamp.com. it was replaced some time after i made the post with "URL submitted by user". why the heck would that have happened?

peace,
david

It's an anti-spam measure: members up to a certain postcount can't post URLs.
Can't say I'm too happy with it either...

Editing posts is possible up to 3 hours after posting.

how many posts? when i posted my earlier reply to this thread i had ~20 posts. certainly not a lot and far more than the typical spammer with a single post.

again, the odd thing was that i remember the url actually working at the time of the post. and then sometime later it was removed. was this a policy that was only recently put into place? and if so, were urls retroactively removed? whatever the case, what an f'ing waste. a dumb, dumb, heavy-handed administrative decision, imo. intentionally losing data that could help people. hopefully the urls are only hidden from public view and not actually deleted.

testing a url: http://winamp.com (winamp dot com)

It's been in place for a few days now.

They are not actually deleted: they are indeed only hidden if a user has less than a certain number of posts.
I guess that certain number is 25, seeing that the links show up now.

(also note that's it's possible to retrieve the links by pressing the quote button under a post)