Need help with an error.

[Angrysteel]

12x <event>ADDON_ACTION_BLOCKED:AddOn 'Mapster' tried to call the protected function 'CompactRaidFrame1:SetPoint()'.
<in C code>: in function `SetPoint'
Interface\FrameXML\FlowContainer.lua:151: in function `FlowContainer_DoLayout':
Interface\FrameXML\FlowContainer.lua:17: in function `FlowContainer_ResumeUpdates':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:186: in function `CompactRaidFrameContainer_LayoutFrames':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:131: in function `CompactRaidFrameContainer_TryUpdate':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:58: in function `CompactRaidFrameContainer_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

nil

Locals:
nil

and

12x <event>ADDON_ACTION_BLOCKED:AddOn 'Mapster' tried to call the protected function 'CompactRaidFrame2:ClearAllPoints()'.
<in C code>: in function `ClearAllPoints'
Interface\FrameXML\FlowContainer.lua:147: in function `FlowContainer_DoLayout':
Interface\FrameXML\FlowContainer.lua:17: in function `FlowContainer_ResumeUpdates':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:186: in function `CompactRaidFrameContainer_LayoutFrames':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:131: in function `CompactRaidFrameContainer_TryUpdate':
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:58: in function `CompactRaidFrameContainer_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

nil

Locals:
nil

I thought this was a Mapster error, but when disabling Mapster, this same error shows up for Lose Control. Disable Lose Control and the same error shows up for Ace 3. Etc etc. I keep disabling addons, but it just seems to randomly pick a different addon and spit this error out.

Any ideas what causing this? Its hard to track down because it only happens in raids, so disabling one addon at a time, or enabling one addon at a time between pulls isnt easy.

[Xrystal]

If the error has only recently started appearing then its likely that Blizz has added another control or 10 to the secured system which won't allow certain things to be done while in combat.

[Phanx]

Blizzard's taint reporting system is almost entirely useless. Post a list of your addons. Maybe someone can tell you which one might be doing something wrong.

[SDPhantom]

Originally Posted by Phanx Blizzard's taint reporting system is almost entirely useless. Post a list of your addons. Maybe someone can tell you which one might be doing something wrong.

A lot of times, Blizzard even taints itself and blames the first addon in its internal list.

[Angrysteel]

Blizzard's taint reporting system is almost entirely useless. Post a list of your addons. Maybe someone can tell you which one might be doing something wrong.

AzCastBar
Addon Control Panel
AutoConfirmRoll
AutoLog
Auto Loot Fix
BadBoy
BetterExtraActionButton
Blizzmove
BlockChinese
BugGrabber
BugSack
Chatter
Chinchilla
Deathnote
DisableProfanityFilter
DXE
EasyMail
EzInterurrupt
FasterCamera
GuildRosterButtons
Inflight
Junkyard
Kgpanels
LeatrixPlus
Macaroon
Mapster
Masque
Omen3
OmniCC
Pitbull4
RaidBuffStatus
RatingBuster
RoleIcons
SharedMedia
Skada
TipTac
WeakAuras
Xloot
Yay Mounts

Those were the addons enabled during the raid, when the messages were appearing.

[Rilgamon]

Dont waste your time. Blizzards raidframe is a mess without addons interfering.
It is broken by design.
Taints for this are easily triggered by addons that not even remotely have something to do with combat or raiding.