Quite a few of my users are experiencing a bug when they use my addon PitBull that when the raid changes (member join/leave/move groups), the entire system will crash.

The following are two of the dumps provided from two different users:

http://pastey.net/56959
http://ace.pastey.net/56960

Edit: put it in a pastey since it's too long.
Edit2: added another.

I am using Pit Bull and have been getting the exact same error. I would attach my dump but it is exactly the same as the first one provided, except for the pc specific info. The first crash occurred Jun 14, 2007 5:32:18.500 PM.

This is a serious issue that needs to be resolved. Nothing in lua should crash WoW (save an infinite loop).

Tons of unit frames are experiencing this issue, it's not just pitbull, and yes it seems like a 2.1 change has caused this. But why some work and some don't, just not sure.

Yes, I've had the problem with Pitbull.

I originally tried out Pitbull, however, after having this problem with X-Perl.

Seems to happen on rapid raid change (e.g. going from one BG straight to another, and a lot of members change quickly), although I've had it happen at the two minute-mark in a BG when the second wave of invites go out and you often get 3-5 more people.

Can someone respond to this? The lua environment should never be able to crash WoW fully.

I crash this way whenever my Tallstrider dies with Grid enabled. >8*(

-hyperactiveChipmunk

Not only Raid changes invite/uninvite or change group crashes WoW. It also happens when I am the group leader and uninvite someone or invite someone into my group does crash WoW.

Also, I was the group leader and when I zone out an instance or zone in. I crash.

If gave me a bunch of error info like from the first post by the PitBull's Author.

I use ag_UnitFrames and have been getting the same thing. =O

So this is what this error is! Yeah, I'm getting the same crash using Pitbull.

Yes, I've heard reports that this is affecting X-Perl, PitBull, ag_UF, and Grid. It likely affects other unit frames as well.

Heh.

When you log in with the latest version of PitBull, it tells you straight up that there's a bug with this version that causes a crash when you join a raid or various other groups. It tells you to use the older version until 2.12, where the error no longer occurs.

Learn to read. =D

---

Q u o t e:
Heh.

When you log in with the latest version of PitBull, it tells you straight up that there's a bug with this version that causes a crash when you join a raid or various other groups. It tells you to use the older version until 2.12, where the error no longer occurs.

---

You do know the guy who wrote the mod, and probably that in game message is the same person who made this post right?

---

Q u o t e:
Learn to read. =D

---

Yeah, can't enter a bg without crashing with agUF. Hell, when I actually get into the bg and I try to attack while mounted that's a crash. I usually have to careeefully dismount a few feet away from the fray and hope that horde don't swarm on me while I lag precariously for a few seconds (during this lag I may or may not crash yet again).

I can confirm this happening with X-Perl, ag_UF and PitBull. I've been swapping out Unit Frame UIs for 2 weeks trying to find one that I like and doesn't crash, no luck as of yet.

As of last week something different happened tho, I had been playing in windowed mode since you pretty much had to hard reboot if it locked up in fullscreen (Windowed allows you to close and reopen wow without a reboot). Now tho, when crashing and coming back into a battleground, I find myself outside the BG when i get back in, but the minimap icon still says im in it. If I leave the BG, while not in the BG using the icon I get hearthed... If I don't click to leave the BG i get the "This battleground will close in 2 minutes" warning, and after 2 minutes I'll get hearthed, no matter where I am.

wtf? When can I have my favorite unit frames back?

I can also safely say I'm having the exact same issue as everyone else. I have 2 accounts setup and running at the same time, and more often than not, they both crash at exactly the same time. This is only a recent problem too, it started about 4 or 5 days ago. Running WoW with PitBull on MacBook Pro 2.33ghz and G4 1.5ghz 12"... Have never had this kind of issue before :) AND looking forward to a fix REAL soon; it was extra bad tonight, happening over and over again.

edit: As a previous poster also stated, there is a message that says this and recommends to downgrade until 2.1.2

"PitBull-r40446 currently has a crashing bug during raids or parties that is solved when WoW 2.1.2 will be released. It is recommended that you revert to PitBull-r39408 until WoW 2.1.2 is released."

---

Q u o t e:
"PitBull-r40446 currently has a crashing bug during raids or parties that is solved when WoW 2.1.2 will be released. It is recommended that you revert to PitBull-r39408 until WoW 2.1.2 is released."

---

Thanks it took me a while to isolate these crashes to PitBull and it's such an awesome UI for me as a healer it's really painful without it. All these crashes just make it unusable, I'll try the earlier release and will see how that goes.

Cheers

This bug sucks.

The consensus on this bug explains so much. Especially with last week being AV weekend. Approximately when 1/3 of the games I joined, my WoW client would either hang, or have a huge (30sec) pause.
I even had a crash on Gruul, and when I tried to reconnect, got another hang. (Really pissed me off as I couldn't loot the quest item off the body)

I had been randomly turning off/upgrading different mods, but never went to the point of disabling PitBull,Grid and ora2.