[ADDON_ACTION_BLOCKED]  AddOn "InlineAura" tried to call the protected function "RandomButtonX:Show()".

function addon:UpdateButtonGlowing(state)
	if true or (state.spellId and IsSpellOverlayed(state.spellId)) or state.highlight ~= "glowing" then

  Hey people.

- You were probably reading this because you hasn't read the "Known issues and limitations" section of the main page. If you had, you wouldn't have come there to post a ticket and found this one. However, I thank you for reading this instead of creating a new, duplicate ticket.
+ This is ticket is here to centralize reports about ADDON_ACTION_BLOCKED errors.

- So, back to business: InlineAura is working like a charm but you get hundreds or errors looking like this during combat :
+ Symptoms : InlineAura is working like a charm but you get hundreds or errors looking like this during combat :
  <<code>>
  [ADDON_ACTION_BLOCKED]  AddOn "InlineAura" tried to call the protected function "RandomButtonX:Show()".
----------------------------------------
  Secondly, it is possible that InlineAura actually causes a taint issue, leading to this error. It might be the code that handles the glowing borders. It uses Blizzard code and might possibly taint it.

- This points means I could fix it ... by removing all glowing border support.
+ This points means I could fix it by altering the glowing border support somehow.
  If you get this kind of error, could you test this please ?

You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #9

  coani Dec 15, 2012 at 13:03 UTC - 0 likes

  The odd part is that I still had occasional highlights with the edit. In any case, using the latest version & trying to keep eye for when the errors are popping up. Was going to check Bugsack & filter the errors, but... now it is throwing an error at me (was fine a few days ago), and it ended up wiping the Bugsack error log (doh). Having just read though about some Blizz taint issues on Buggrabber's page, I start to wonder if the errors I've seen lately are related to those. Will keep eye open.

• 

  • Reply
  • #8

  Adirelle Dec 09, 2012 at 14:11 UTC - 0 likes

  So, what you are saying is that disabling highlighting, be it Blizzard's or built-in, stop the errors ?

• 

  • Reply
  • #7

  coani Dec 09, 2012 at 13:28 UTC - 0 likes

  Slowpoke update but, I still get those errors, though less frequently than before. Seems to happen more often if I'm flipping between bars in combat, though it also happens on the main bar without flipping. I wanted to say it happens more frequently on macro'd buttons, but most of the time, it's buttons 5+ that are blanking out, while my first buttons are usually the most macro'd. Most of the time I need to wait till I'm out of combat to get the buttons to update, though sometimes flipping the bars back & forth seems to get them displayed again, though there was one case yesterday where the buttons suddenly refreshed in midcombat out of the blue (first time I seen that happen).

  While I was using the previous version with the "true or" edit, I had no issues at all.

  The errors I get are on MultiBarX:Show calls and ActionButton5-12:Show.

• 

  • Reply
  • #6

  Adirelle Nov 10, 2012 at 15:16 UTC - 0 likes

  In lastest alpha, I've added a "private" overlay glow. This should avoid tainting Blizzard stuff but it could also have other side effects. Could you test it please ?

• 

  • Reply
  • #5

  coani Nov 09, 2012 at 00:37 UTC - 0 likes

  As a quick note from my side, I tried this "true or" edit in my setup today, and so far had 0 errors after messing around in raids & whatnot. I was used to getting spammed by errors all the time, especially from macro'd buttons, so it's been a nice change to see no errors at all :)

• 

  • Reply
  • #4

  Adirelle Nov 08, 2012 at 18:22 UTC - 0 likes

  Just send the big one. I'll sort it on my side. The taint log records everything though a lot of tainting is innocuous (e.g. tainting global variables that are never used by Blizzard code).

  However, if you have a very reproducible way of producing this error. You can enable the taint log just before it happens and shut it down just after. This should make a shorter log.

  Last edited Nov 08, 2012 by Adirelle
• 

  • Reply
  • #3

  mfrnka Nov 08, 2012 at 15:22 UTC - 0 likes

  Thanks for your work in trying to track it down and fix this.

  Messed with it for a while today. As you may have guessed, running no other addons and a fresh install of Inline Aura, it will not taint. Loading a number of other addons and the log is full of taint issues from a number of different addons and Ace libraries.

  I'll try to narrow them down one by one in combination with Inline Aura, but that's a slightly longer project.

• 

  • Reply
  • #2

  Adirelle Nov 08, 2012 at 06:57 UTC - 0 likes

  So could you try another thing please ?

  1. Revert the changes you've done.
  2. In game, in the chat, type "/console taintLog 2".
  3. Play until you get the addon blocked error message (it's better you have a way to reproduce it at will).
  4. Type "/console taintLog 0".
  5. Go in your WoW installation folder. In the "logs" subfolder, there should be a "taint.log" file. Zip it and attach it here please.

  Last edited Nov 08, 2012 by Adirelle
• 

  • Reply
  • #1

  mfrnka Nov 07, 2012 at 22:14 UTC - 0 likes

  Small edit to Display.lua adding "true" as above stopped the errors for me.