newest version of winamp likes to crash alot
 

i don't know if anyone else has been getting this but since the latest version my winamp crashes alot, mainly when im updatnig id3 tags and stuff itll crash at random times.

I don't know if anyone else has been catching this but winamp just seems to becoming less stable with each version. Im about to downgrade to an older version, does anyone remeber the version of winamp right before the new media library icons came out? i remeber i had no problems with that one

5.13

-daz

i agree with the id3 tag crashing. for me it seemed to correlate more with id3v2. i'll report more on it as i see it.

I've had tagging crashes as well. And they appear to be random. This has been happening for me since 5.21. Originally, the bug appeared to correlate with copying from ID3v2 to v1, but I'm not so sure anymore.

http://forums.winamp.com/showthread....hreadid=240920

Mine does the tagging crashes too, but I've been living with that since around 5.08 or so...

Does it still happen after a clean install with no 3rd-party plugins?

Post a list of all plugins (including defaults) c/o a my_plugins_list.txt as generated by DrO's gen_nunzio plugin (see here for info/instructions)

The same thing used to happen to me quite a bit, especially when an Explorer window was open which contained the files I was editing at the time (damn WinXP and it's Tiles/Info views). But it hasn't happened to me since I disabled a few 3rd-party plugins I never used, and updated a few others.

Yup that's it! :) Thanks ..

Here's my plugin list. It's difficult to test with a clean install because it doesn't always happen - seems to be pretty random. Still happens pretty often though, usually when editing the same field in lots of files at once...

Ah ha! Good call on the Windows Explorer business. I haven't had any crashes while explorer windows are closed. Does this behavior constitute a bug? Theoretically, Winamp should fail gracefully in this case, or detect file locks, and wait a few seconds for them to free up.

So, is this a bug or what?

My winamp is crashing too, just like the way you guys said.
I've been using Winamp since version 1.x n' I've never had any error such as this one.

Btw, I've also tryed to close all explorer's windows, but this error insists.

PS: I'm using version 5.24

@ViPPeR_666

Well, like everyone else in this thread, maybe you can confirm whether it only happens when the files you're editing are also open in an Explorer window at the time? If not, then your issue is being caused by something else, ie. different to the cause for everyone else in this thread.


@bemymonkey

If it's been crashing since 5.08, then it's more than likely some 3rd-party plugin to blame, because the problem seemed to appear around the 5.2x versions for just about everyone else here (including me).

Does it still crash after removing/disabling all these 3rd-party plugins?
Monkey's Audio Player v4.01 [in_APE.dll]
WinLIRC Plugin 0.4 [GEN_IR.DLL]
MessengerAmp v2.2 (gen_msn.dll)
Play Tracking Replacement v0.4 [gen_pcfix.dll]
AudioScrobbler for Winamp v1.1.10 (ML Mode) [ml_audioscrobbler.dll]
gUSB v1 build 005 [ml_gusb_us.dll]

@DJ Egg

I'm afraid to tell you that this is not, apparentaly, a problem with the plugins. I have these plugins since version 4.x n' I've never had any sort of error.

This is the first time. What do you think I should do?

Oh yea, I've also tryed to close all explorer windows, including mIRC (lol?). N' this error just keeps on.

What plugins? You haven't even posted a plugin list, heh (see above).

If a newer version of Winamp starts crashing for no apparent reason, then the first place to look is always at 3rd-party plugins. As certain (core) changes are made to Winamp, then some 3rd-party plugins can become broken, and therefore the author(s) of said plugin(s) need to update them to make them compatible again.

btw, there was no Winamp 4.x

I've deleted all my plugins. There's only one left:

[moo] Announce

Btw, I couldn't find his dll name.

I've removed the plugins and I'm testing now... By the way, how do you "disable" a plugin without uninstalling it? Thanks for the continued efforts to help! This forum would be dead without you, heheh.

The easiest way is to close Winamp, and then go to the Winamp\Plugins folder and rename the respective plugins to something like gen_msn.dll.off

(of course, it helps to know the filenames of said 3rd-party plugins first).

This way you can always easily re-enable them at a later date by renaming them back again (ie. with no need to do an official uninstall/reinstall).

Aaaaaah, now why didn't I think of that? lol :)

Thanks for the tip :D

Well, that gen_nunzio plugin that Egg mentioned above will show the actual name of the plugin (.dll) and the text file generated will show it as well.

This is happening to me as well, as I posted here. As far as I can tell it's not caused by any plugin.

@ tankexmortis

So it's nothing to do with having an Explorer window open containing the files that you're editing at the time (as was the case with just about everyone else who posted in this thread)?

Also, unless you post a my_plugin_list.txt log, then there's no way for us to know if it's being caused by a 3rd-party plugin or not.


@ bemymonkey

Any joy since disabling those plugins? Or does it still crash?

No, it happens even without any Explorer windows open. As for the plugins, I disabled everything without "Nullsoft" in front of it's name and got the same error. I'm assuming that's all of the third party plugins?

It's still crashing :-(... not that this is going to impair my Winamp usage ;-)...

Guess I'm gonna have to start using ID3-Tagit more often...

New development: recently, after crashing, upon reopening Winamp it takes longer than usual to load, and then it immediately freezes.
This is really frustrating. If the next update (or someone's kind help) doesn't fix this problem I'm giving up and switching to (ugh) iTunes.

Nevermind, a clean install fixed the random freezing. Still having the original problem, of course.

The 'random crashing when editing id3 tags' issue is fixed for 5.25