I was looking a combat log this morning and realized that taint.log had grown to be almost a gigabyte in size. Most of it was warnings from ATT similar to these:

12/16 21:24:51.566  An action was blocked in combat because of taint from AllTheThings - CompactRaidFrame15:ClearAllPoints()
12/16 21:24:51.566      Interface\FrameXML\FlowContainer.lua:157 FlowContainer_DoLayout()
12/16 21:24:51.566      Interface\FrameXML\FlowContainer.lua:17 FlowContainer_ResumeUpdates()
12/16 21:24:51.566      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:185 CompactRaidFrameContainer_Layou
tFrames()
12/16 21:24:51.566      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:130 CompactRaidFrameContainer_TryUp
date()
12/16 21:24:51.566      Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:57 CompactRaidFrameContainer_OnEven
t()
12/16 21:24:51.566      CompactRaidFrameContainer:OnEvent()

and

12/17 01:22:12.962  An action was blocked in combat because of taint from AllTheThings - CompactRaidFrame2:Show()
12/17 01:22:12.962      Interface\FrameXML\CompactUnitFrame.lua:376 CompactUnitFrame_UpdateVisible()
12/17 01:22:12.962      Interface\FrameXML\CompactUnitFrame.lua:307 CompactUnitFrame_UpdateAll()
12/17 01:22:12.962      Interface\FrameXML\CompactUnitFrame.lua:203

I'll have to remember to keep an eye out for this... I wonder if the taint.log gets reset often or not, but I have nothing in there from AllTheThings. In fact I only have 3 separate 'action was blocked' messages entirely.

If you ever manage to track down a specific action or event which causes a message concerning AllTheThings to go into the taint log, please post the details because I have nothing to go off of locally concerning these actions. ATT has no references or use of any of the frame names mentioned in your logs, so I'm really not sure where to look in the code.

It's strange. Since opening this issue and deleting my log to get fresher reports, I haven't seen it again. I'll close this out and keep an eye on it. If it happens again I'll reopen it.

There are recent reports #656 now of various things relating to 'CompactRaidFrames' and how ATT is being blocked from using protected functions on them... so there probably is some overlap but I don't have any idea how code is being shuffled around in the game for ATT to be trying to call functions on raid frames...
Being able to specifically replicate an issue is our first step to tackling that problem so hopefully someone finds how that can be done and posts it. Could be related to this taint log issue... not sure.

Yah, that could certainly be the same thing. I'm seeing the same error in BugSack (the ClearAllPoints one).