1. #1

    Addons preventing aura cancels?

    So lately, it seems a few of my addons are preventing me from clicking off buffs, bringing up a UI error when I try to (despite the fact that I've got UI error window disabled). These addons are:

    Auctioneer (Auc-Advanced)
    AuctionLite
    Chatter

    Why the hell are Auction and Chat addons screwing with buffs? And I'm sure it's them, because as soon as I disable all three of them (and I tested disabling one at a time), I can click off buffs just fine.

    This is the error I get when trying to click off a buff, and it only happens the first time:



    Code:
    Date: 2010-12-29 14:17:14
    ID: 3
    Error occured in: AddOn: AuctionLite
    Count: 1
    Message: Error: AddOn AuctionLite attempted to call a forbidden function (CancelUnitBuff()) from a tainted execution path.
    Debug:
       [C]: CancelUnitBuff()
       ..\FrameXML\BuffFrame.lua:280: BuffButton_OnClick()
       [string "*:OnClick"]:1:
          [string "*:OnClick"]:1
    AddOns:
      Zoom, v
      Swatter, v5.9.4960 (WhackyWallaby)
      AucAdvanced, v5.9.4960 (WhackyWallaby)
      AucFilterBasic, v5.9.4960 (WhackyWallaby)
      AucFilterOutlier, v5.9.4960.2531
      AucMatchUndercut, v5.9.4960.2531
      AucStatSales, v5.9.4960.2842
      AucStatStdDev, v5.9.4960 (WhackyWallaby)
      AucStatWOWEcon, v5.9.4960.2530
      AucUtilAHWindowControl, v5.9.4960.3311
      AucUtilAppraiser, v5.9.4960.2530
      AucUtilAskPrice, v5.9.4960.3175
      AucUtilAutoMagic, v5.9.4960.3142
      AucUtilCompactUI, v5.9.4960.2530
      AucUtilEasyBuyout, v5.9.4960.3583
      AucUtilFixAH, v5.9.4960 (WhackyWallaby)
      AucUtilGlypher, v5.9.4960.2545
      AucUtilItemSuggest, v5.9.4960.3108
      AucUtilPriceLevel, v5.9.4960.2545
      AucUtilScanButton, v5.9.4960.2530
      AucUtilScanFinish, v5.9.4960.2530
      AucUtilScanProgress, v5.9.4960.2530
      AucUtilScanStart, v5.9.4960.4819
      AucUtilSearchUI, v5.9.4960.3655
      AucUtilSimpleAuction, v5.9.4960.4546
      AucUtilVendMarkup, v5.9.4960.2530
      AuctionLite, v1.7.1
      Babylonian, v5.1.DEV.130
      Chatter, v1.0
      Configator, v5.1.DEV.278
      DBMCore, v
      DebugLib, v5.1.DEV.275
      Gnosis, vv2.03
      Grid, vr1361
      GridIndicatorCornerIcons, v40000-1
      GridIndicatorSideIcons, v40000-1
      GridStatusRaidIcons, v30200-2
      HideBlizzard, v1.0.51
      Omen, v3.0.9
      PowerAuras, v4.4
      RazerNaga, v1.0.1
      RazerNagaCast, v
      RazerNagaRoll, v
      RazerNagaTotems, v
      RazerNagaXP, v
      ShadowedUnitFrames, vv3.3.1
      Skada, v1.2-27
      SkadaAbsorbs, v1.0
      SkadaCC, v1.0
      SkadaDamage, v1.0
      SkadaDamageTaken, v1.0
      SkadaDeaths, v1.0
      SkadaDebuffs, v1.0
      SkadaDispels, v1.0
      SkadaEnemies, v1.0
      SkadaFailbot, v1.0
      SkadaHealing, v1.0
      SkadaPower, v1.0
      SkadaThreat, v1.0
      Stubby, v5.9.4960 (WhackyWallaby)
      BlizRuntimeLib_enUS v4.0.3.40000 <us>
      (ck=6b4)
    Quote Originally Posted by Precursor View Post
    "Fall of therzane....." ....um what? if that woman fell , god help us it will be the second cataclysm
    Words that lots of people don't seem to know the definition of:
    "Troll", "Rehash", "Casual", "Dead", "Dying", "Exploit".

  2. #2
    I read an explanation of this issue on the DBM support forums from the author. Basically, there are two ways to code an addon in LUA; one is using global variables and function names and the other is using private limited-scope variables and function names. In the former, if the coder uses a global variable or function name he runs the risk of having that variable or function conflict with another variable of the same name within blizzard's add-on code. This issue is also known as "tainting".

    I'm not using the addons that you are, but i'm experiencing the same issue when trying to cancel an aura or inspect someone. In your case, since you have identified the addon(s), you could appeal to the author to fix his tainting issue or simply stop using the addon(s).

    by the way, the reason you are getting that error pop-up even though the blizzard setting is turned off, is because you have Swatter installed. It's intended to a 'friendly' lua error handler and I believe it comes installed with quite a few addons, including auctioneer. you can type /swat to see it's options
    Last edited by Spottswoode; 2010-12-29 at 07:58 PM.

  3. #3
    Spottswoode, that is not right. That error means you are calling a protected function from tainted code (untrusted; e.g. addon code). CancelUnitBuff() was changed to a protected function between 4.0.0 and 4.0.3. Try updating your addons.

  4. #4
    Deleted
    Quote Originally Posted by Woogs View Post
    Spottswoode, that is not right. That error means you are calling a protected function from tainted code (untrusted; e.g. addon code). CancelUnitBuff() was changed to a protected function between 4.0.0 and 4.0.3. Try updating your addons.
    He's very much right. Look at the debug stack printed, it's a direct function call from frameXML. Only way this can be caused is by tainting of a var it uses.

  5. #5
    Quote Originally Posted by Woogs View Post
    Spottswoode, that is not right. That error means you are calling a protected function from tainted code (untrusted; e.g. addon code). CancelUnitBuff() was changed to a protected function between 4.0.0 and 4.0.3. Try updating your addons.
    All of them are updated to the latest versions, except Chatter, which hasn't been updated since 3.2 or so...I think. But this error comes from Auctioneer too, which was updated in 4.0.3.
    Quote Originally Posted by Precursor View Post
    "Fall of therzane....." ....um what? if that woman fell , god help us it will be the second cataclysm
    Words that lots of people don't seem to know the definition of:
    "Troll", "Rehash", "Casual", "Dead", "Dying", "Exploit".

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •