First: I know that there have been other similar reports and that you said that it's not the fault of AuctionMaster, but please read on!
What steps will reproduce the problem?
1. Optional step: Make sure that AuctionMaster is the only enabled addon.
2. Do the daily quest Riding the Storm. There are other ways to reproduce it but this one is the easiest I know.
3. Use the quest item to get on a mob.
4. Attack it a few times.
5. Use the leave vehicle button.
What is the expected output? What do you see instead?
The message "Interface action blocked by addon" is shown. If you have BugGrabber installed, it will show the error directly, otherwise you can use /console taintLog 2 before to get it written to the file taint.log.
What version of the product are you using?
Do you have an error log of what happened?
11/18 13:18:54.696 An action was blocked in combat because of taint from AuctionMaster - CompactRaidFrame1:Show()
11/18 13:18:54.696 Interface\FrameXML\CompactUnitFrame.lua:276 CompactUnitFrame_UpdateVisible()
11/18 13:18:54.696 Interface\FrameXML\CompactUnitFrame.lua:234 CompactUnitFrame_UpdateAll()
11/18 13:18:54.696 Interface\FrameXML\CompactUnitFrame.lua:96
Please provide any additional information below.
The fact that this taint also happens if AuctionMaster is the only enabled addon clearly shows that there must be something in AuctionMaster that affects the CompactRaidFrames. AuctionMaster doesn't have to call the function itself to cause this error. As soon as the Blizzard code uses any tainted variable it will fail. Most likely AuctionMaster causes this error because it sets (and therefore taints) many global variables with common names (e.g. frame, height, slot, bag, now, bt). I assume one of this variables is then used by Blizzard code which causes the taint error.
I've attached a file that lists all global variables that are set by AuctionMaster. If you want to check your code yourself I suggest to use either FindGlobals or the Wow Global Finder GUI wrapper for it.
- 7 comments