WoWInterface - Swatter Error

WoWInterface (https://www.wowinterface.com/forums/index.php)

- nUI: Bug Reports (https://www.wowinterface.com/forums/forumdisplay.php?f=90)

- - Swatter Error (https://www.wowinterface.com/forums/showthread.php?t=23674)

Just got an Error through Swatter.

New DK, lvl 55. I was just hopping onto a very tiny horse I was stealing for the quest and saw the notice run through chat. Doesnt appear there are any problems at the moment. I have not reloaded at all and everything works fine.

I'm using the Dev release and here's the error.

Code:

Date: 2009-05-17 00:17:57

ID: 1

Error occured in: AddOn: nUI

Count: 10

Message: Note: AddOn nUI attempted to call a protected function (updateFunc()) during combat lockdown.

Debug:

  [C]: updateFunc()

  ..\FrameXML\AnimationSystem.lua:14:

      ..\FrameXML\AnimationSystem.lua:10

  ..\FrameXML\AnimationSystem.lua:35:

      ..\FrameXML\AnimationSystem.lua:29

AddOns:

  Swatter, v5.5.4187 (WombatII)

  Ace3, v

  AdvancedTradeSkillWindow, v

  AraBrokerGuildFriends, vr17

  Armory, v6.4.1

  ArmoryGuildBank, v6.2

  AucAdvanced, v5.5.4187 (WombatII)

  AucFilterBasic, v5.5.4187 (WombatII)

  AucFilterOutlier, v5.5.4187.2531

  AucMatchUndercut, v5.5.4187.2531

  AucScanData, v5.5.4187 (WombatII)

  AucStatClassic, v5.5.4187 (WombatII)

  AucStatHistogram, v5.5.4187 (WombatII)

  AucStatiLevel, v5.5.4187 (WombatII)

  AucStatPurchased, v5.5.4187 (WombatII)

  AucStatSales, v5.5.4187.2842

  AucStatSimple, v5.5.4187 (WombatII)

  AucStatStdDev, v5.5.4187 (WombatII)

  AucStatWOWEcon, v5.5.4187.2530

  AucUtilAHWindowControl, v5.5.4187.3311

  AucUtilAppraiser, v5.5.4187.2530

  AucUtilAskPrice, v5.5.4187.3175

  AucUtilAutoMagic, v5.5.4187.3142

  AucUtilBigPicture, v3.0.3.1

  AucUtilCompactUI, v5.5.4187.2530

  AucUtilEasyBuyout, v5.5.4187.3583

  AucUtilItemSuggest, v5.5.4187.3108

  AucUtilPriceLevel, v5.5.4187.2545

  AucUtilScanButton, v5.5.4187.2530

  AucUtilScanFinish, v5.5.4187.2530

  AucUtilScanProgress, v5.5.4187.2530

  AucUtilSearchUI, v5.5.4187.3655

  AucUtilSimpleAuction, v5.5.4187.0

  AucUtilVendMarkup, v5.5.4187.2530

  Auditor2, v4.0

  Babylonian, v5.1.DEV.130

  Bagnon, v1.7.2

  BagnonForever, v1.1.1

  BagnonOptions, v

  BagnonTooltips, v

  BankItems, v30002

  BeanCounter, v5.5.4187 (WombatII)

  BrokerAuditor, v1.0

  BrokerRaidSave, v1.5

  Carbonite, v3.12

  ClearFont2, v2.6

  Configator, v5.1.DEV.130

  DayveItemSocketHelper, v

  DebugLib, v5.1.DEV.130

  Enchantrix, v5.5.4187 (WombatII)

  EnchantrixBarker, v5.5.4187 (WombatII)

  EventAlert, v4.2.15

  Factionizer, v30100.1

  FishingBuddy, v0.9.7c

  Fortress, v1.11-beta4 

  FuBar2Broker, vr83-release

  FuBarGuildFu, v2.4

  GetToThePoint, v$Revision: 1094 $

  GuildCheck, vv2.23

  HKCounter, v

  idHitThat, v3.0.9.1

  Informant, v5.5.4187 (WombatII)

  ItemRack, v

  LilSparkysWorkshop, v0.72

  MarketWatcher, v1.02

  nUI, v5.03.02 (Dev)

  nUIConfigGUI, v30100.2

  nUIGlossBlack, v1.01.00

  nUIHUDLevel, v30000.3

  nUIInfoPanelCarbonite, v

  nUIInfoPanelGuildChat, v2.01.00 (WoW Version 3.1.0)

  Overachiever, v0.40

  OverachieverTabs, v0.40

  OverachieverTrade, v0.40

  PhanxChat, v3.1.0.40-beta

  Postal, v3.1.1

  RatingBuster, v

  SickOfClickingDailies, v6

  SilverDragon, vv2.3.1

  Skada, v1.0

  SkadaAbsorbs, 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

  SlideBar, v5.5.4187 (WombatII)

  Stubby, v5.5.4187 (WombatII)

  Talented, v2.2

  TradeskillInfo, v1.4.1

  TradeskillInfoUI, v1.4.1

  Volumizer, v3.1.1-1.1.3

  zBrokerDurability, v1.3

  ZOMGBuffs, v$Revision: 58 $

  ZOMGBuffsBlessingsManager, v$Revision: 58 $

  ZOMGBuffsLog, v$Revision: 58 $

  ZOMGBuffsPortalz, v$Revision: 58 $

  ZOMGBuffsSelfBuffs, v$Revision: 58 $

  (ck=b50)

If there's any one thing I hate about the new secure frames system it's those error messages. Everything in that message tells me where the problem happened in Blizzard's code and contains nothing to tell me where in my code the taint occurred /sigh

Unfortunately, there's nothing I can do at this point because there's just no indication whatsoever where in the code this taint occurred. We'll need to keep an eye on this and see if we can find a pattern to it so I can home in on where it's originating.

Thanks for reporting it and *please* everyone, if you see similar errors, try to post here as well... the more detail you can provide the better.

That was the first one that actually caused Swatter to pop up. It didn't affect the usability of nUI+ so I wasn't horribly concerned.

There were a few more errors that same night. I'll go through my Swatter logs and post all the top portions of the errors with the info and counts, I dont think you want to see all the addons again and again, lol.

Another error that swatter hit:

Happened mid jump off a cliff while mounted. I had just used Alt-M into and out of the Blizz map. I'm curious why it has Carbonite tagged also. Is that because that is the info panel I had showing at the time also?

Code:

Date: 2009-05-20 02:14:18

ID: 2

Error occured in: AddOn: nUI

Count: 2

Message: Note: AddOn nUI attempted to call a protected function (WorldFrame:SetPoint()) during combat lockdown.

Debug:

  [C]: SetPoint()

  [string "*:OnHide"]:1:

      [string "*:OnHide"]:1

  [C]: Hide()

  ..\FrameXML\UIParent.lua:1495: SetUIPanel()

  ..\FrameXML\UIParent.lua:1340: ShowUIPanel()

  ..\FrameXML\UIParent.lua:1280:

      ..\FrameXML\UIParent.lua:1276

  [C]: SetAttribute()

  ..\FrameXML\UIParent.lua:1899:

      ..\FrameXML\UIParent.lua:1887

  [C]: ShowUIPanel()

  Carbonite\Carbonite.lua:4268: BTWM()

  Carbonite\Carbonite.lua:9279: ToggleFrame()

  [string "TOGGLEWORLDMAP"]:1:

      [string "TOGGLEWORLDMAP"]:1

AddOns:

-----removed addons list------

  (ck=c2d)

Yeah... I've got to find a solution to that problem... that occurs when you open and close the world map while in combat because nUI is trying to move the viewport which is not allowing in combat lockdown.