Please update your addons

[WOWVern]

Sounds simplistic enough. Let me clarify:

Some addons are causing WoW to crash in the loading screen with "Load Out of Date Addons" checked. I believe Blizzard has made it mandatory (due to the Background Downloader being run) to have as many addons up to date as possible. It means more work, but in the long run it makes the game run smoother.

[Cairenn]

Ummm, what? (a) Who are you talking to? (b) Blizz has made it mandatory? What the heck are you talking about?

[Haleth]

You're on a site dedicated to WoW addons, I think that the general idea of updating addons is understood.

If addons are causing a crash on your loading screen then you either a) are using too many addons, causing a lack of RAM memory which would be very unlikely; b) using a broken addon which should either be updated by yourself if a new version is available or by the author.

Try deleting your WTF, Cache and Data/Cache folders also (make backup of the WTF folder).

[reflectional]

This was happening to me so i disabled a few addons that i didn't need at that moment and everything ran fine.

[tiker]

Just an FYI, I've read so far that Recount and FishingBuddy addons are causing crashing / hanging issues for people.

My wife had a problem and was able to logon after disabling FishingBuddy but leaving Recount enabled.

Just putting it out there.

[SDPhantom]

Usually when a patch comes out, WoW breaks several addons in the process. Now, I login with one of my addons breaking the WoW chat/command system. Oh, how the tables have turned.

Originally Posted by WOWVern Some addons are causing WoW to crash in the loading screen with "Load Out of Date Addons" checked.

One of my own addons that uses code to dynamically throttle itself has been acting strangely in a way similar to this in which the throttle no longer functions properly and causes the game to hang for short periods of time. Doing an open-ended scan causes the game to run into an infinite loop which the throttle code was supposed to prevent.

Edit: I found the problem, the great minds at Blizzard decided to screw up the function GetTime() so the value returned only updates once every frame.

[Saiket]

Originally Posted by SDPhantom Edit: I found the problem, the great minds at Blizzard decided to screw up the function GetTime() so the value returned only updates once every frame.

Yep, you can either use time(), which only has second precision, or debugprofilestart()/debugprofilestop() which has sub-millisecond precision but might interfere with legitimate debug timers.

[Lily.Petal]

Recount breaks with every patch though. Not sure on FishingBuddy

Originally Posted by tiker Just an FYI, I've read so far that Recount and FishingBuddy addons are causing crashing / hanging issues for people. My wife had a problem and was able to logon after disabling FishingBuddy but leaving Recount enabled. Just putting it out there.

OT: Sadly, both of my main computers are not working right meow; updated my mac and now won't start and my laptop's screen broke. Might be a while before I look/update or start on a project :<

[Zidomo]

Both Recount & FishingBuddy have put out updated 4.3 release versions in the past day (Recount actually has been updated to 4.3 in WowAce alpha versions for close to a month).

Neither of them are on this site; check Curse.