since 2.4 I get some weird WOW crashes (whiting seconds I'm d/c'ed on login-screen). However this is happening very infrequently and only if I'm tanking and have several mobs targeting me (happened in PVP as well if I get targeted by many players).
It doesn't happen at all if I turn all my mods off, so I guess it is related to at least one of them.
I haven't tried to figure out which mod does cause it, since I can't easily reproduce the d/c and I'm using to many addons to make this simple (however it is one that got updated since it also happens if I don't load the out of date addons).

What I'd like to know now is, is there any way to track those crashes, or what caused them even though I don't get an errormessage but get d/c'ed right away.

Thanks

btw, I'm running wow on a Mac

There is a wow crash error log that is found in the World of Warcraft folder...
I think there is more information on this in the Offical Forums technical support.

Although it might be simpler just to turn off one at a time until you find the one that is causing the problem. By the sounds of it, if it happens when things are targeting you it is a Unitframe addon of some sort or maybe a raid assist something that activates in some fashion to let you know who is targeting you.

Whittle down the mods like this it will speed up the process instead of the one at a time thing.

1. Turn off all mods-- Do you crash? If yes then there is an error in the install of the game . -- Run the repair utility. If no then step 2.

2. Turn on the first half of your mods. Do you crash? If yes then you know the mod is in that section you turned on. If no then step 3.

3. Turn off the first half of your mods and turn on the second half. Do you crash? If yes then the offending mod is in the second half. If no then you have got a bigger problem of two mods conflicting and that is such a joy to figure out.

If you find the error in one half of your mods then just start turning off one half of the mods still on till you find the mod causing the problems.

I hope that all made sense.

What mod's are you running as i know a few have error grabbing and reportting functions (Auctioneer) and you might be able to use a existing mod to trouble shot your problem

Thank you all very much for the responses, I couldn't find an error report in the WOW folder so I'll go ahead and use the turn on/off of mods to figure out what it could be. This could take a while since I got a few...

Atlas
Atlasloot
Auctioneer (with the ones it adds like Beancounter....)
Cartographer
CT RABossMod
Druid bar (out of date, but still works, and as mentioned I crashed as well when I didn't load out of date addons)
Energy watch v2
EnhTooltip
Examiner
Gatherer
Improved Error Frame
Informant
Mail to next
Minimap Button Frame
MobInfo
Nature ECB
Omen2
OmniCC
Outfitter
Recount
Reputation Session Tracker
SCT
Titan Panel
X-Perl (just recently added this, and it crashed already before I had it)
YACL
Deadly Boss Mods

Well I don't notice anything HORRIBLY bad except one glaring issue. Cart and Gather. That's not good as both do the same and can be a little hoggish on the memory. You have CTRABM but not CTRA? Get rid of it as DBM does that work for you and MUCH better. OmniCC was notorious for locking up UIs if you have the cooldown pulse enabled and get silenced for your majority spellcast school. For example-if I got silenced as a lock casting a shadowbolt, nearly 80% of my actionbar items would pulse when the silence is over. that massive graphics pulse used to lock me down for 2-3 seconds (but it's fixed now)

Have you totally blown away your SCT folder and redownloaded it since 2.4? Also, you may have to delete the WTF files for SCT and let it create a virgin setup. I had major issues with SCT until I killed the addon and the saved configs.