Does anyone else have issues with being disconnected while in a raid and then logging back in to a total game lockup when it tries to load the UI?

My system:

Dimension 5150, Intel Pentium DProcessor 930 (3.0 GHz)
2GB DDR2 SDRAM at 533MHz
128MB Radeon ATI X600 video card

Addons:

Nurfed General
Nurfed Action Bars
Nurfed Unit Frames
CTRA
CTRA Boss Mods
CT master mod
Damage Meters 5.0
Spellalert
AB Info bars

I tried cleaning my registry and old drivers, then installing the catalyst 5.1 drivers, but to no avail. If I'm disconnected for whatever reason and then try to log back in while in a raid, my system soft locks and I have to close WoW. As raid leader, this is highly frustrating. Anyone had this issue or any idea how to resolve it?

[FOCUS] Perhaps a tech support thread is in order?

Disable all your UI mods, then one by one enable them until you hang again. I have Nurfed General, Nurfed Action Bars, CTRA, CTRA Boss Mods, and Damage Meters, as well as other mods, and never have experienced this issue.

Lots of people I know have this problem... and they find it stems from all the spam in the Ctra channels as you log in... One simple solution is to NOT disable any of the mods but just have yourself booted from the raid before you log on... works everytime. Reinvite. Good to go.

A bunch of people in our guild has it (me included). For most people, kicking them from raid when they're ld will allow people to login about 95% of the time.

However even when kicked from raid, if I log in when people are fighting, I'll still lock up. It does not seem add-on related per se, but more related to a huge amount of bandwidth spam you get upon logging in (current combat + "group change" notifications for 39 ppl + all buff/health info + all ctra/ktm spam).

I agree extremely frustrating for the raidleader though, because you can't just wait until you're linkdead, but you have to wait until you're linkdead enough for the raidleadership to change (raidleader can't be /kicked, even from (A)'s.)

It's usually CTRA, that thing lags like hell.

This happens to me all the time. I pretty much always have to ask on Vent to get kicked from the raid anytime I get disconnected, or else I just can't log back in. I've never tried to pinpoint it, but supposedly it's related to RaidAssist.

Yeah, usually I just wait a couple minutes till raid leader passes to someone else, then I have them kick me. I'll try having someone boot me from the CTRA channel and see if that works.

If you get kicked from the raid you will still be in the raid channel and should still receive the spam, in other words the situation should not have changed. I can imagine the idea with kicking someone from the raid is to stop CT_RA from actually competing for CPU time while under massive load from the initial loading of WoW graphics systems and whatever. Disabling CT_RA should do the same though, so beats me.

Yes it will, becuase it puts you under the threshold of "how much spam can i take before i lock up".

There's two different things that can spam you:

1) Logging into a raid. When you login, you have to get the group updates and health/buff updates for 40 people + whatever mobs. This is regardless of whether you have ctra or not.
2) The ctra/ktm channel shit on top of it.

Being kicked from raid removes 1) which quite for obvious reasons is the larger component of the spam. It's not the channel spam *alone*, it's the channel spam along with everything else that's going on that puts it over the tipping point.

The one thing I was curious about but never had time to check was whether the lockup is clientside or serverside. Recall that in early patches (1.2-1.3ish), you'd go linkdead by jumping and spinning around in ironforge (some anti-spam bandwidth threshold kicked in and booted you). I'm wondering if that's the same case here; though if it were you'd expect everyone to be affected by it, not just certain people.

Isn't that bug still there? Or maybe I'm mistaking it with something else. If you jump and spin around on your kodo, for example, really quick you will still get disconnected as far as I know. Doesn't seem to relate to that problem.

Edit: But I do agree with your assessment :)