error

[meggsy]

Hi i keep getting this error now and before since last patch and swatter i can't understand what is causing this causes my char to pause for a second very 3o secs.
this is the error i get. Decursive comes up as you have a lot off errors which will affect your game but swatter only brings this up any help will be appreciated.

Date: 2012-04-29 07:03:27
ID: 1
Error occured in: Global
Count: ∞
Message: ..\FrameXML\UIParent.lua line 2672:
attempt to compare nil with number
Debug:
(tail call): ?
[string "*:OnLoad"]:6:
[string "*:OnLoad"]:1
[C]: ?
..\FrameXML\UIParent.lua:2672:
..\FrameXML\UIParent.lua:2659
AddOns:
Swatter, v5.13.5258 (BoldBandicoot)
Altoholic, v4.3.001
AucAdvanced, v5.13.5258 (BoldBandicoot)
AucFilterBasic, v5.13.5258 (BoldBandicoot)
AucFilterOutlier, v5.13.5258.5187(5.13/embedded)
AucMatchUndercut, v5.13.5258.5232(5.13/embedded)
AucScanData, v5.13.5258 (BoldBandicoot)
AucStatHistogram, v5.13.5258 (BoldBandicoot)
AucStatiLevel, v5.13.5258 (BoldBandicoot)
AucStatPurchased, v5.13.5258 (BoldBandicoot)
AucStatSales, v5.13.5258.4838(5.13/embedded)
AucStatSimple, v5.13.5258 (BoldBandicoot)
AucStatStdDev, v5.13.5258 (BoldBandicoot)
AucStatWOWEcon, v5.13.5258.4828(5.13/embedded)
AucUtilAHWindowControl, v5.13.5258.5133(5.13/embedded)
AucUtilAppraiser, v5.13.5258.5241(5.13/embedded)
AucUtilAskPrice, v5.13.5258.5160(5.13/embedded)
AucUtilAutoMagic, v5.13.5258.5224(5.13/embedded)
AucUtilCompactUI, v5.13.5258.5254(5.13/embedded)
AucUtilEasyBuyout, v5.13.5258.5241(5.13/embedded)
AucUtilFixAH, v5.13.5258 (BoldBandicoot)
AucUtilItemSuggest, v5.13.5258.5224(5.13/embedded)
AucUtilPriceLevel, v5.13.5258.5241(5.13/embedded)
AucUtilScanButton, v5.13.5258.5153(5.13/embedded)
AucUtilScanFinish, v5.13.5258.5153(5.13/embedded)
AucUtilScanProgress, v5.13.5258.4979(5.13/embedded)
AucUtilScanStart, v5.13.5258.5153(5.13/embedded)
AucUtilSearchUI, v5.13.5258.5254(5.13/embedded)
AucUtilSimpleAuction, v5.13.5258.5210(5.13/embedded)
AucUtilVendMarkup, v5.13.5258.4828(5.13/embedded)
Babylonian, v5.1.DEV.312(/embedded)
BadBoy, v9.009
BagBrother, v
Bagnon, v4.3.19
BagnonForever, v1.1.3
BagnonTooltips, v
BeanCounter, v5.13.5258 (BoldBandicoot)
BloodShieldTracker, v0.16
ButtonFacade, v4.2.375
ButtonFacadeCaith, v4.0.62
ButtonFacadeTrinity, v40000.1
caelCCBreak, v
caelEmote, v
caelInterrupt, v
caelLib, v
caelMedia, v
caelNameplates, v
caelQuests, v
caelThreat, v
Chatter, v1.0
Configator, v5.1.DEV.312(/embedded)
Cooldowns, v
DataStore, v4.3.001
DataStoreAchievements, v4.3.001
DataStoreAgenda, v4.3.001
DataStoreAuctions, v4.3.001
DataStoreCharacters, v4.3.001
DataStoreContainers, v4.3.001
DataStoreCrafts, v4.3.001
DataStoreCurrencies, v4.3.001
DataStoreInventory, v4.3.001
DataStoreMails, v4.3.001
DataStorePets, v4.3.001
DataStoreQuests, v4.3.001
DataStoreReputations, v4.3.001
DataStoreSpells, v4.3.001
DataStoreStats, v4.3.001
DataStoreTalents, v4.3.001
DBMCore, v
DebugLib, v5.1.DEV.312(/embedded)
Decursive, v2.7.0.5
Dominos, v4.3.4
DominosBufftimes, v
DominosCast, v
DominosRoll, v
DominosTotems, v
DominosXP, v
DXELoader, v
Edge, v788
Enchantrix, v5.13.5258 (BoldBandicoot)
EnchantrixBarker, v5.13.5258 (BoldBandicoot)
Factionizer, v4.3.0
FerousMedia, v1.6
FishingBuddy, v1.0.7i
GladiatorlosSA, vv1.0
Glance, v4.3.4.1
GlanceArmor, v4.3.4.1
GlanceClock, v4.3.4.1
GlanceDualSpec, v4.3.4.1
GlanceDungeons, v4.3.4.1
GlanceEmblems, v4.3.4.1
GlanceFrameRate, v4.3.4.1
GlanceFriends, v4.3.4.1
GlanceGold, v4.3.4.1
GlanceGuild, v4.3.4.1
GlanceLatency, v4.3.4.1
GlanceLocation, v4.3.4.1
GlanceMemory, v4.3.4.1
GlanceMounts, v4.3.4.1
GlancePets, v4.3.4.1
GlanceProfessions, v4.3.4.1
GlanceReputation, v4.3.4.1
GlanceTemplate, v4.3.4.1
GlanceTolBarad, v4.3.4.1
GlanceWinterGrasp, v4.3.4.1
GlanceXP, v4.3.4.1
GoGoMount, v4.3.5
GTFO, v4.12.3
IceHUD, v1.7.10 (Revision: 870)
Impulse, v783
Informant, v5.13.5258 (BoldBandicoot)
iSold, v
kgPanels, v1.7
LibExtraTip, v5.12.DEV.319(/embedded)
LightHeaded, v344
MacroBank, v1.10
ManaCore, v788
Masque, v4.2.375
MasqueCaith, v4.2.76
MasqueTrinity, v40300.1
MikScrollingBattleText, v5.6.113
MisDirectionHelper2, vv4.3.0.1
MogIt, v2.3.0
mRunes, v1.25
Omen, v3.1.6
Overachiever, v0.65
OverachieverTrade, v0.65
PartySpotter, vv5.17.70000
PitBull4, vv4.0.0-beta30
PitBull4Aggro, vv4.0.0-beta30
PitBull4Aura, vv4.0.0-beta30
PitBull4Background, vv4.0.0-beta30
PitBull4BlankSpace, vv4.0.0-beta30
PitBull4Border, vv4.0.0-beta30
PitBull4CastBar, vv4.0.0-beta30
PitBull4CastBarLatency, vv4.0.0-beta30
PitBull4CombatFader, vv4.0.0-beta30
PitBull4CombatIcon, vv4.0.0-beta30
PitBull4CombatText, vv4.0.0-beta30
PitBull4ComboPoints, vv4.0.0-beta30
PitBull4ExperienceBar, vv4.0.0-beta30
PitBull4HealthBar, vv4.0.0-beta30
PitBull4HideBlizzard, vv4.0.0-beta30
PitBull4Highlight, vv4.0.0-beta30
PitBull4HostilityFader, vv4.0.0-beta30
PitBull4LeaderIcon, vv4.0.0-beta30
PitBull4LuaTexts, vv4.0.0-beta30
PitBull4MasterLooterIcon, vv4.0.0-beta30
PitBull4PhaseIcon, vv4.0.0-beta30
PitBull4Portrait, vv4.0.0-beta30
PitBull4PowerBar, vv4.0.0-beta30
PitBull4PvPIcon, vv4.0.0-beta30
PitBull4QuestIcon, vv4.0.0-beta30
PitBull4RaidTargetIcon, vv4.0.0-beta30
PitBull4RangeFader, vv4.0.0-beta30
PitBull4ReadyCheckIcon, vv4.0.0-beta30
PitBull4ReputationBar, vv4.0.0-beta30
PitBull4RestIcon, vv4.0.0-beta30
PitBull4RoleIcon, vv4.0.0-beta30
PitBull4Runes, vv4.0.0-beta30
PitBull4Sounds, vv4.0.0-beta30
PitBull4ThreatBar, vv4.0.0-beta30
PitBull4VisualHeal5, vv4.0.0-beta28
PitBull4VoiceIcon, vv4.0.0-beta30
Postal, v3.4.13
Prospect, vv201108061219
Quartz, v3.0.8
Reforgenator, v1.3.17
SaySapped, v2011-07-01
SexyMap, v1.3
sheepdog, v1.0.6
SilverDragon, vv2.6.2
SimpleILevel, v3.0.14
SimpleILevelGroup, v3.0.14
SimpleILevelResilience, v3.0.14
SimpleILevelSocial, v3.0.14
Skada, v1.3-11
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
Skillet, v
SLDataText, v4.0.6
SlideBar, v5.13.5258 (BoldBandicoot)
SmartBuff, v4.3a
SpellFlash, v5.110.1
SpellFlashDeathKnight, v1.06
SpellFlashRacials, v2.6.9
SpellFlashX, v1.0.8 Beta
SpellFlashCore, v1.49.2
Spy, v
StealthAlerter, v0.99.13
Stubby, v5.13.5258 (BoldBandicoot)
SwindlerPreventer, v4.3.3
TipHelper, v5.12.DEV.315(/embedded)
TipTac, v11.09.29
TipTacItemRef, v11.09.29
TipTacTalents, v11.09.29
TomTom, vv40300-1.4.4-541092e
TradeSkillMaster, vv1.3.1
TradeSkillMasterAccounting, vv1.1
TradeSkillMasterAuctionDB, vv1.2
TradeSkillMasterAuctioning, vv1.1.6
TradeSkillMasterItemTracker, vv1.0.2
TradeSkillMasterMailing, vv1.0.2
Tycoon, v789
TycoonContent, v789
WoWLazyMacros, vr10
ZygorGuidesViewer, v3.3
ZygorTalentAdvisor, v2.0.240
BlizRuntimeLib_enUS v4.3.4.40300 <us>
(ck=197f)

[Seerah]

It looks as if perhaps one of your addons has a global variable that is overwriting a value in the default UI or is otherwise messing with the UIFrameFlash_OnUpdate function in another way.

I'm afraid that you may have to do a binary search if you cannot think of any changes/updates you made to addons when this problem began.

It looks as if this page on Phanx's site is down at the moment, but here's a copy-paste of the cached version:

Troubleshooting WoW Addons This guide will walk you through the steps of troubleshooting a WoW addon. If you’re experiencing a problem with an addon, troubleshooting will often allow you to fix the problem yourself, without having to wait for a response to a bug report or a forum post. Even if you can’t fix the problem yourself, troubleshooting is still useful, because it will give you lots of helpful information to include in a bug report. Remember, the more information you can give an addon's author, the more likely it is that they will be able to fix the problem, and the less time it will take them to do it. Don’t be daunted by the size of this guide. It’s broken down into eight simple steps, and each step not only provides instructions, but also explains why the step is useful. Once you've gone through the steps once or twice, you can skip the explanations, and the guide seems a lot shorter! Step 1: Is there really a problem with the addon? Occasionally WoW just flakes out and does really weird stuff. This is almost always caused by corrupted data in its cache files. Deleting these cache files will force WoW to make new, uncorrupted cache files. To clear the cache, completely exit WoW, find the following folder, and delete everything inside of it: ...\World of Warcraft\Cache\WDB\ Now relaunch WoW and log back in. If the problem doesn’t happen anymore, then you’re already done! Step 2: Is the addon is installed correctly? If the addon appears in the in-game addon manager (at the character selection screen, press the red “AddOns” button in the lower left corner) then the addon is installed correctly, and you can skip to Step 3. If the addon does not appear in the addon manager, then the problem is on your computer, not in the addon. In order for WoW to find an addon, it must be in a particular place, with a particular arrangement of files and folders. The most common causes of installation problems include extra folders added by some decompression utilities (including the one built into Windows), extra folders included by confused addon authors, and decompression utilities that don’t preserve file paths. To verify that an addon is correctly installed, find its TOC file. Correct: ...\World of Warcraft\Interface\AddOns\CoolMod\CoolMod.toc Incorrect: ...\World of Warcraft\Interface\AddOns\ CoolMod.toc ...\World of Warcraft\Interface\AddOns\CoolMod-v1.3\CoolMod\CoolMod.toc ...\World of Warcraft\Interface\AddOns\Interface\AddOns\CoolMod\CoolMod.toc If the files are in the wrong place, simply putting them in the right place should fix the problem. Step 3: Is the addon actually enabled? If the in-game addon manager shows the addon’s name in gold with a yellow check mark next to it, then the addon is enabled, and you can skip to Step 4. If there is a silver check mark, or no check mark, click the checkbox until a yellow check mark appears. If the addon’s name is now shown in gold, then the addon is now enabled, and you can skip to Step 4. If the addon’s name now appears in red, then there is a problem that prevents WoW from loading the addon. Look to the right of the addon’s name for an explanation. The two most common reasons are: “Out of date” means that the addon hasn’t been updated since the last major WoW patch. In most cases, this does not mean that the addon won’t work. Most patches don’t change anything that affects most addons, so most addons do not need to be updated for every patch. Simply enable the “Load out of date addons” option at the top of the addon list. You should never change the interface number in the addon’s TOC file; not only is this unnecessary, but also means that you have no way to tell whether any problems you have with the addon are caused by changes in WoW that the addon wasn’t updated for, or by problems in the addon itself. “Dependency disabled” means that the addon depends on another addon; you must also enable that other addon before this one can be loaded. You can see the dependency by placing the mouse cursor over the addon’s title and reading the tooltip. Enabling the listed dependency should allow this addon to be loaded. There are a few other reasons why an addon isn't loadable, but you won't see them very often. “Banned” means that the addon has been banned by Blizzard. This may apply to the addon as a whole, or just to a particular version of the addon. You should check the addon’s download page or contact its author, to find out more. “Incompatible” means that the addon hasn’t been updated since the last patch that Blizzard felt was so major that all addons absolutely had to be updated for it. The only patch where this was done was Patch 2.0, back in 2006. Likewise, I bet you can guess what “Dependency incompatible” means. If no update is available for this addon (and/or any addons it depends on), then you can no longer use it. Step 4: Does the addon have a LoadManager? Open the addon’s TOC file in Notepad or another plain-text editor. If it does not list a LoadManager, you can skip this step. If the addon lists a LoadManager, then essentially the addon is telling WoW “don’t load me at login, because this addon will load me later if I’m needed.” An addon might do this to keep itself from being loaded before it’s needed (for example, if you’re not in a battleground, you don’t need a battleground helper addon yet) or to prevent itself from being loaded on some classes (for example, if you’re not a shaman, you don’t need a totem timer addon). The general idea is that addons are only loaded if and when they are actually going to be used. However, if you have an addon installed that’s listed as a LoadManager for other addons, but it’s not enabled, then none of the addons that list it as a LoadManager will ever be loaded, even if they are enabled. If the addon lists another addon as a LoadManager, and you have that addon installed, make sure it is enabled. Step 5: Is there an in-game error message? By default, WoW does not show addon errors. To enable their display, open the Interface Options window, navigate to the Help panel, and check the “Display Lua Errors” option. (Lua is the programming language in which addons, and the default UI, are written.) Now log out and back in, and try to reproduce the problem. When it happens, you might see a dialog box appear on the screen containing an error message. Copy the full text of the error message, and paste it in your bug report. Please note that you should copy only the error message, not the list of local variables or the list of installed addons which sometimes appear after it in the dialog box! In nearly all cases it’s just useless junk that the author has to scroll through when reading your ticket; in the rare event that the author wants this information, (s)he will ask for it. Step 6: Does the problem happen with other addons disabled? This is important because addons can interfere with each other if they try to do the same thing, or if they interact with Blizzard’s code in unusual ways. Log out and disable all addons except the one you’re troubleshooting. If the addon has any dependencies (identified in step 2) or a LoadManager (identified in step 3), enable those too. Now log back in. If the problem still happens, skip the rest of this step. If the problem doesn’t happen anymore, though, you’ll need to do a little more detective work to find out which addon it’s conflicting with. The quickest way to do this is called a “binary search”. Enable half of your addons and log in. If the problem doesn’t happen, log out, disable the enabled addons, and enable the other half of your addons. Once you find the half with the problem, disable half of those. Repeat the procedure until you’re left with a single addon that seems to trigger the problem when enabled alongside the addon you’re troubleshooting. Step 7: Does the problem happen with the addon’s default settings? Each addon saves its settings in a separate file. Depending on the addon, this file may be shared between all characters on your account, or there may be one file for each character, or there may be both a shared file and character-specific files. Saved variables that are shared between all characters are located in: ...\World of Warcraft\WTF\Account\<AccountName>\SavedVariables\<AddonName>.lua Saved variables that are specific to one character are located in: ...\World of Warcraft\WTF\Account\<AccountName>\<ServerName>\<CharacterName>\SavedVariables\<AddonName>.lua If the addon stores a lot of data (like Auctioneer or LootLink) or takes a long time to set up, you should back up the file to another location before deleting it, so you can restore it later if it turns out not to be the problem. Otherwise, just delete it. Now log in. If the problem doesn’t happen anymore, then it was probably caused by bad data in your settings file. At this point, you should usually just reconfigure the addon from its default settings. However, if the problem reappears after you reconfigure the addon, or if your configuration was very complex, you can send the addon’s settings file(s) the addon’s author, and they can try to figure out what the specific problem is, and whether they can do anything to fix it. Step 8: Report the problem! Once you’ve gone through the above steps, you should report the problem to the addon’s author so he or she can fix it. Be sure to include all the information you can. If you’re not sure what you should include, feel free to copy the list below and use it as a template for your report! What version of the addon are you using? Please provide the actual version number, and don’t just say “latest” or “newest”! What locale (language) do you play WoW in? What is the problem? What were you doing when it happened? Be as specific as possible! What is the exact text of the error message that accompanies the problem, if any? (Step 5) Does the problem happen when all other addons are disabled? If not, which addon is it conflicting with? (Step 6) Does the problem happen with the addon’s default settings? (Step 7) If the problem doesn’t happen with the addon’s default settings, attaching your saved variables file is helpful. If the problem is graphical (eg. something on the screen looks wrong), attaching a screenshot is helpful. If the addon’s ticket tracking system doesn’t support attachments, you can upload the file or screenshot to a file- or image-hosting service, and include the URL to it in the ticket. Remember to check on your bug report after a few days. The addon’s author may need more information from you in order to identify or fix the problem, or they may not be able to reproduce the problem themselves and ask you to try a possible solution. If you have any questions or comments about this guide, feel free to send me (Phanx) a private message on WoWInterface.com or WoWAce.com.

[meggsy]

Originally Posted by Seerah It looks as if perhaps one of your addons has a global variable that is overwriting a value in the default UI or is otherwise messing with the UIFrameFlash_OnUpdate function in another way. I'm afraid that you may have to do a binary search if you cannot think of any changes/updates you made to addons when this problem began. It looks as if this page on Phanx's site is down at the moment, but here's a copy-paste of the cached version:

Nice thanks again the wiping of the WDB fixed the pausing sigh.
Still getting same error -frame one - disabled most add ons and still get it i make sure the add ons i use are very new otherwise i take them off e.g. changed sexy map with pocket one always use np also your tip add-on I'm changing to it again deleted hogg add ons e.g. althoholic .
The trouble is most great authors are living the game in droves and hard to get fixes.After every patch i go through same problem by the time i fix everything and works right they put out new patch same problems.
They can't even fix there own buggs and create headaches if it wasn't for the hours I've put in i wouldn't be playing it.
Thank you heaps again you've helped so much.

edit after 6 hours playing around i got it down to this not sure how to fix it

Date: 2012-04-29 12:24:44
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\PitBull4_VisualHeal5\VisualHeal.lua line 16:
Usage: NewModule(name, [prototype, [lib, lib, lib, ...]): 'name' - Module 'VisualHeal' already exists.
Debug:
(tail call): ?
[string "*:OnLoad"]:6:
[string "*:OnLoad"]:1
[C]: ?
[C]: ?
Ace3\AceAddon-3.0\AceAddon-3.0.lua:260: NewModule()
PitBull4_VisualHeal5\VisualHeal.lua:16: in main chunk
[C]: LoadAddOn()
PitBull4\Main.lua:1135: LoadModules()
PitBull4\Main.lua:1246: OnProfileChanged()
PitBull4\Main.lua:1312:
PitBull4\Main.lua:1283
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9:
[string "safecall Dispatcher[1]"]:5
(tail call): ?
Ace3\AceAddon-3.0\AceAddon-3.0.lua:543: EnableAddon()
Ace3\AceAddon-3.0\AceAddon-3.0.lua:636:
Ace3\AceAddon-3.0\AceAddon-3.0.lua:621
[C]: LoadAddOn()
..\FrameXML\UIParent.lua:274: UIParentLoadAddOn()
..\FrameXML\UIParent.lua:348: TimeManager_LoadUI()
..\FrameXML\UIParent.lua:614:
..\FrameXML\UIParent.lua:582

[Phanx]

Originally Posted by Seerah It looks as if this page on Phanx's site is down at the moment ...

It's not down, but I did move the page to a new, shorter URL. I've added a redirect now, so you can get there using the old URL again.

[meggalo]

Search frame xml in your add ons folder and you'll find the add-on doing the damage

[meggsy]

Originally Posted by meggalo Search frame xml in your add ons folder and you'll find the add-on doing the damage

Thanks a lot that was annoying me so m ugh not to mention my game was suffering.
Found that cael threat i was using is the culprit