17 - Taints in 4.3
What steps will reproduce the problem?
- starting the taint.log logging (/console taintLog 1)
- doing something including combat (for me, using the RaidFinder was one way of getting these)
- "An action was blocked in combat"
What is the expected output? What do you see instead?
Everything "works" as normal, except for the taints happening (and maybe interfering with raid frames, when people join/leave the group infight)
What version of the product are you using?
6.65
Do you have an error log of what happened?
Not an error but the entries of the taint.log ...
12/27 22:45:55.724 Global variable CHAT_FRAME_TAB_NORMAL_NOMOUSE_ALPHA tainted by BasicChatMods - ¨ÿ6p†:8 ?() 12/27 22:45:55.724 Interface\AddOns\BasicChatMods\BasicCore.lua:38 ?() 12/27 22:45:55.724 Interface\AddOns\BasicChatMods\BasicCore.lua:7 12/27 22:45:55.724 Execution tainted by BasicChatMods while reading CHAT_FRAME_TAB_NORMAL_NOMOUSE_ALPHA - Interface\FrameXML\FloatingChatFrame.lua:1273 FCFTab_UpdateAlpha() 12/27 22:45:55.724 Interface\FrameXML\FloatingChatFrame.lua:2134 FCFDock_UpdateTabs() 12/27 22:45:55.724 Interface\FrameXML\FloatingChatFrame.lua:1386 oldFCF_DockUpdate() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CombatLog\Blizzard_CombatLog.lua:3556 FCF_DockUpdate() 12/27 22:45:55.724 Interface\FrameXML\UIParent.lua:2014 <unnamed>:UIParentManageFramePositions() 12/27 22:45:55.724 Interface\FrameXML\UIParent.lua:1347 12/27 22:45:55.724 <unnamed>:SetAttribute() 12/27 22:45:55.724 Interface\FrameXML\UIParent.lua:2021 12/27 22:45:55.724 UIParent_ManageFramePositions() 12/27 22:45:55.724 Interface\FrameXML\BuffFrame.lua:348 BuffFrame_UpdateAllBuffAnchors() 12/27 22:45:55.724 Interface\FrameXML\BuffFrame.lua:120 12/27 22:45:55.724 BuffFrame_Update() 12/27 22:45:55.724 Interface\FrameXML\BuffFrame.lua:49
as well as
12/27 22:45:55.724 An action was blocked in combat because of taint from BasicChatMods - CompactRaidFrame28:SetAttribute() 12/27 22:45:55.724 Interface\FrameXML\CompactUnitFrame.lua:184 CompactUnitFrame_SetUpClicks() 12/27 22:45:55.724 Interface\FrameXML\CompactUnitFrame.lua:44 12/27 22:45:55.724 CreateFrame() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:343 CompactRaidFrameContainer_GetUnitFrame() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:315 CompactRaidFrameContainer_AddUnitFrame() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:267 CompactRaidFrameContainer_AddPets() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:183 CompactRaidFrameContainer_LayoutFrames() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:131 CompactRaidFrameContainer_TryUpdate() 12/27 22:45:55.724 Interface\AddOns\Blizzard_CompactRaidFrames\Blizzard_CompactRaidFrameContainer.lua:63 CompactRaidFrameContainer_OnEvent() 12/27 22:45:55.724 CompactRaidFrameContainer:OnEvent()
Please provide any additional information below.
While of course BCM doesn't touch the CompactRaidFrames, Blizzard thinks it does. It seems they are now quite sensitive to taining and "touching" a function or frame might get the whole frame tainted. :( Seems to be some discussion going on at WowInterface (http://www.wowinterface.com/forums/showthread.php?t=41974), maybe that helps you?
BCM is not the only addon having these seemingly non-related problems. I think, Everdreamer explains it nicely in Altoholic's taint issue: http://wow.curseforge.com/addons/altoholic/tickets/498-the-long-standing-taint-issue/ .
| User | When | Change |
|---|---|---|
| funkydude | Apr 15, 2012 at 19:48 UTC | Changed status from Replied to Fixed |
| ckaotik | Jan 21, 2012 at 11:52 UTC | Changed status from Waiting to Replied |
| funkydude | Jan 19, 2012 at 01:16 UTC | Changed status from New to Waiting |
| ckaotik | Dec 28, 2011 at 12:57 UTC | Changed description:=== Please provide any additional information below. === While of course BCM doesn't touch the CompactRaidFrames, Blizzard thinks it does. It seems they are now quite sensitive to taining and "touching" a function or frame might get the whole frame tainted. :( Seems to be some discussion going on at WowInterface (http://www.wowinterface.com/forums/showthread.php?t=41974), maybe that helps you? + + BCM is not the only addon having these seemingly non-related problems. I think, Everdreamer explains it nicely in Altoholic's taint issue: http://wow.curseforge.com/addons/altoholic/tickets/498-the-long-standing-taint-issue/ . |
| ckaotik | Dec 28, 2011 at 11:30 UTC | Create |
- 5 comments
- 5 comments
- Reply
- #5
funkydude Apr 15, 2012 at 19:48 UTC - 0 likesHopefully fixed now.
- Reply
- #4
Dexter74 Mar 26, 2012 at 07:45 UTC - 0 likessimilar problem, error messages are only active when BasicChatMods
- Reply
- #3
ckaotik Jan 23, 2012 at 10:10 UTC - 0 likesYet another update: After disabling the config.lua in the .toc file, raid frames are completely usable again :) So it seems to be the drop downs, indeed.
- Reply
- #2
ckaotik Jan 21, 2012 at 11:52 UTC - 0 likesApparently, the fade module taints the aforementioned variable CHAT_FRAME_TAB_NORMAL_NOMOUSE_ALPHA. Disabling that part of BCM seems to help to some degree.
So, here's the list of variables that get reported in a standard random dungeon run:
Most of these only appear up to ten times, however UIDROPDOWNMENU_MENU_LEVEL is a totally different story. I would think this is the main cause of our troubles :(
However, I still get taints which cause the default UI raid frames to become unusable. One example would be people leaving/joining a ground in combat - frames that need to be created, hidden, shown or moved don't get touched, messing up all raid frames. Worst case: Someone in the earlier frames leaves and WoW only shifts part of the old frames because they are tainted. Then, whenever I target someone "after" the last "safe" frame, I get a random target instead :( Sucks when healing.
- Reply
- #1
ckaotik Dec 28, 2011 at 12:57 UTC - 0 likesReference to Altoholic's similar problem added.