I'm getting tired of the problem that causes raid addons to lock up the game when you login while in raid, or even sometimes when joining a raid or battleground. Strangely this doesn't happen when you do a /console reloadUI. If you're lucky enough to make it past the lockup without getting disconnected, the UI memory usage could go up towards serveral 100 MB afterwards.
I've tried to fight the symptoms. Some say doing UIParent:UnregisterEvent("RAID_ROSTER_UPDATE") helps, but I am not sure why it would. Now I've tried putting raid frame creation and display on a schedule in the branch version of ag_UnitFrames, and I think it helps, but it means that you won't see any unit frames until you leave combat, which sucks too if you're disconnected in an important PvE raid.
The problem didn't happen before 2.1. So it's new to 2.1, and I suspect it might be because of a change in blizzards raid header code. But I don't know.
Finding the cause of this problem would be worlds better than trying to fight all the symptoms. People say it happens with XPerl, ag_UnitFrames and PitBull, Grid, and I would guess that CTRaid, PerfectRaid and sRaidFrames are affected too. If this is indeed a blizzard introduced bug, we should find it and report it instead of doing silly workarounds. If you use multiple addons which use raid headers (for example aguf+Grid, PitBull + sRaidFrames) please try to disable one of them to see if you still get the lockups. Please report back here with the results, no matter the outcome. I'd like to know if it's all addons which cause it, or only a few.
Hopefully I am not the only one concerned with this problem. I will now try to create a minimal addon using raid headers to see if I can isolate the problem. If you have anything to share regarding this problem, please post it here!:)
For me using a few days old version of Pitbull (r39408) --> No Lockups/Crashes at all.
Using any newer version --> Lockups/Crashes.
Grid is installed too, but until now didnt cause any problems.
Seeing as this is affecting a whole bunch of addons or might even occur with the default ui...seems like a major bug introduced with the latest patch.
If you crash during a raid and can?t login anymore...try having your raidleader kick you out of the raid and then reconnect (and if successful, get reinvited within 1 minute of course :) ).
For me using a few days old version of Pitbull (r39408) --> No Lockups/Crashes at all.
I had exactly one crash. AddOn: Pitbull r38408 ... so we have a little conflict ;)
Several of our raidmembers had that bug during Raids - Addons (afaik):
Xperl, Perl, Pitbull, ag_UF, Grid and sRaidframes
If you arn't successful with Catharrs method of fixing the bug, try to save WTF and Interface folder.
Lunch WoW without any addons. Then log in and move your char a few yd. Then log out and lunch WoW with the addons again. Should work, cause it did to everyone in our raid.
If it doesn't work at all.... hey... it's Blizz *shrugg*
For what it's worth, I use the newest version of Pitbull (i.e., the one that says, "this will crash you, revert now"), along with Grid, oRA, and lots of other such mods. I've never had a single crash, and I've done raids, battlegrounds, and so forth. Obviously if I do have a crash, I'll revert as recommended, but it's definitely not automatically reproducable just by using the newest versions of mods like Pitbull.
Some say doing UIParent:UnregisterEvent("RAID_ROSTER_UPDATE") helps, but I am not sure why it would.
This is a confusion on erm, someone's part. This cures the jittering you get when someone joins/leaves/zones in a raid group. Entirely different cause and effect. But, let's move on:
I found the main causes are during zoning and between (and including) PLAYER_LEAVING_WORLD and PLAYER_ENTERING_WORLD (whether that's logging in for first time, or zoning into a BG). I can only assume when there's a lot of memory being shuffled around and some race condition is being hit. A garbage collection at some key point for example. Which would explain why it appears to be so random and entirely different from person to person. Noone has the same memory config, logs into same location, has same mods and options and so on.
The only luck I've had, like andreasg, is to avoid changing attributes for header templates between these times. And ran into same problems if you get into combat when you log in.
I keep poking more at it, but as you all know, there's precious little you can do to debug it when the game quits out after the long freeze. Will try and put some BIG notice in middle of screen with some timing info tomorrow. You do get a single frame again before the disconnect comes through so with a big enough font and some coffee it might help. But man it sucks, trial and error debugging with a 3-5 min wait between each try.
Thought for a time it might be the error catcher working overtime with some ACTION_BLOCKED things. Anyway, going to go over everything again if 2.1.2 patch was not done this week. /sigh
If only some Dev would run a profiler or something against WoW.exe during these times... /wave Devs
I run Pitbull (downladed daily from WAU) for party,player,target,tot,totot, focus,focustarget, and X-perl (From ui.worldofwar.net) for raid frames with everything else with in xperl disabled. iv been in BG's, Partys, Raids - join'ed and left in and out of combat and i have not experianced what you are describing here.
*i'll get my system spec's for you when i get home :D
Hate to be a devil's advocate here, but...yes, client crashes are Blizzard's problem, ultimately. But only to an extent. If one build of PitBull is triggering party-invite crashes and an earlier (or later) build is not, Blizzard is not 100% to blame for those crashes.
Its similar to the old "do you blame C for a program's memory management issues or the program itself?" (and so on). The limitations & potential dangers in (a version of) a language must be accounted for in the development of a program (mod). As the devs here are of course aware :). Of course. if the dangers/limitations are undocumented or unreferenced, accounting for them in your code becomes more problematic.
The continual crashes when being invited to a 5-man party here only started occurring on June 14 after a PitBull commit on that date (no other system changes). They went away with a later commit, before I switched back to SimpleUnitFrames. But r40279 had the following load warning put in it by the author (which continues in the latest builds): "("|cffffff7fPitBull|r-" .. PitBull.version .. " currently has a crashing bug during raid that is solved when WoW 2.1.2 will be released. It is recommended that you revert to |cffffff7fPitBull|r-r39408 until WoW 2.1.2 is released.""
So is it PitBull that has a crashing bug, is it Blizzard, or a combination of both (as I suggest above)? Yes, Blizzard should not have their LUA environment allowing UI mods that utilize it causing crashes. But until then, UI mods should not be doing things in that environment which can trigger crashes.
Then again, if it happens consistently with the default Blizzard frames with no other frame mods active, mods are likely less to be to blame. I don't see evidence of this yet, though; only unit frame mods causing the crashes.
Of course, its often a trade off between making your mod do what you want it do the way you want to do it on one hand. And on the other hand, working around the problems in the buggy LUA environment that can cause major user issues. As a different example, a few patches ago, a few inventory mods which scanned a user's mailbox caused WoW lockups when doing so (SimpleBankState & CharacterInfo/CharacterInfoStorage are the ones I tested that did so). But author changes to such mods worked around this problem without altering their functionality.
Good luck with PitBull; hope it turns out great.
EDIT: posts went up prior to submitting this, including Ckknight's request for system stats. So here is mine (abbreviated):
--Self-built circa-2003 3GHz Intel P4 with 1 GB of RAM
--Windows XP Pro
--ATI 9700 Pro video card. Upgraded to (latest as of the date) Radeon 7.5 drivers on June 3/07. Reverted back to previously used (stable in WoW) Radeon 6.9 drivers (Oct '06) trying to debug the crash problem. No more crashes after first disabling PitBull & moving to SimpleUnitFrames, then later reverting to that earlier ATI 6.9 driver revision. ATI Windows drivers have a noted history of crashing WoW (& Everquest & Half-Life 1, etc. etc.) with various revisions.
Remember everyone that the topic of this thread is not a crash per see, but more a lockup that lasts for around 3 minutes before kicking you to the login screen. This is a lockup and will not force the wow client to close.
This I think is unrelated to the 132 error/crash seen lately.
The times where I didn't get kicked to the login screen, FuBar_PerformanceFu reported memory usage of over 100-200mb by ag_UnitFrames.
Prior to today, I had no issues with lockups and PitBull. I was always solo or in a group with one other person. Today I was in a group of 4 people (total) for a brief time and all was well, but when the 5th person joined I locked up and was booted, then crashed trying to relog in. I reverted to the version mentioned in the login print, and had no further issues.
Dell Inspiron 9300
Intel Pentium M 1.86GHz + 1GB RAM
Nvidia GeForce Go 6800
Used Grid and PitBull at the same time (with and without PitBull's raid frames enabled) with no problems whatsoever. Stopped using Grid maybe a week ago and have been using PitBull raid frames ever since. Never experienced any crash or lockup, and I update all addons at least once a day, so I've used many different revisions. I'm continuing to use latest PitBull despite the warning, unless and until I experience problems with it.
I had the freeze issue 3 or 4 times over the weekend while using Pitbull, but not this evening. Over the weekend, it happened twice with 3 people in the party and once after 2 5-man runs. I locked, but didn't notice my mem usage, as I was leaving the instance. Ignoring the warnings (added after my freezes), I did not revert and have been running in a party with one other person with no issues. I was briefly in an instance with a 5-man group earlier and had no trouble when I entered or left. I'm running a newer revision of Pitbull, since I updated right before logging in.
AMD Athlon XP 3000+
1 GB matched DDR
ATI Radeon 9800 Pro
Windows XP Pro (hmmm, maybe I should try it on my linux partition for kicks...)
Shuttle SN27P2 XPC
AMD AM2 64 X2 4200 (65w) CPU
2 x 1Gb Corsair TWIN2X2048-6400 C4 PRO
Sparkle Gforce 7950GT 512mb
Win XP sp2
Using Aguf & Sraidframes when raiding (typically a version no older than 1 or 2 days, updating via wowace updater).
The problem doesn't occur for me when I disable Sraid/Aguf and load Ctra instead. As mentioned in the other thread, the lockups can also be avoided by getting kicked out of the raid before logging back in. It happens only when I'm relogging while in a raid group.