WowAce

Using version ag_UnitFrames-r709.zip, got this error, which caused my WoW client to crash back to the login screen...

Error occured in: Global
Count: 1
Message: ...\AddOns\ag_Extras\modules\castbar\castbar.lua line 284:
aUFFontString99:SetText(): Font not set

Trace stack...
SetText()
   ...\AddOns\ag_Extras\modules\castbar\castbar.lua:284:method()
      ag_UnitFrames\ag_UnitFrames.lua:971:
         ag_UnitFrames\ag_UnitFrames.lua:959

This error happened while in an AB BG, and I was standing there, a horde rode up to me, and was about to hit me for the first time. I had him targeted. Maybe when he started casting a spell the error happened? Knocked me back to the login screen, and client was flaky after relogging in.

here is my Dump report with more detail.

["message"] = "...terface
AddOns
ag_Extras
modules
castbar
castbar.lua:284: aUFFontString146:SetText(): Font not set",

["count"] = 42,

["addons"] = " Swatter, v5.6.4409 (KangaII)\n WowheadLooter, v30201\n NPCScan, v3.2.0.5\n agExtras, vr709\n agUnitFrames, vr709\n Bartender4, v4.4.1\n Cartographer, v2.0\n CartographerCoordinates, v2.0\n CartographerFoglight, v2.0\n CartographerLookNFeel, v2.0\n CartographerNotes, v2.0\n CartographerWaypoints, v2.0\n CartographerZoneInfo, v2.0\n DBMCore, v\n ErrorMonster, v3\n FluidFrames, v2.3\n FuBar, v\n FuBarRestFu, vv1.3.2\n MagicRunes, v1.0.63\n MagicRunesIconDisplay, v1.0.63\n MagicRunesRuneBars, v1.0.63\n Mendeleev, v3.0\n PlayerLinkMenu, v\n Portfolio, v1.21\n Postal, v3.2.0\n RangeRecolor, v2.1\n RatingBuster, v\n RecipeBook, v\n Recount, v\n SwindlerPreventer, v3.2\n TipTac, v09.08.27\n TipTacItemRef, v09.08.13\n TipTacTalents, v09.08.13\n BlizRuntimeLib_enUS v3.2.0.30200 <us>\n (ck=312)\n",

["timestamp"] = "2009-09-02 18:03:11",

["context"] = "Global",

["stack"] = "[C]: ?\n[C]: in function `SetText'\n...terface
AddOns
ag_Extras
modules
castbar
castbar.lua:284: in function `method'\nInterface
AddOns
ag_UnitFrames
ag_UnitFrames.lua:971: in function <Interface
AddOns
ag_UnitFrames
ag_UnitFrames.lua:959>\n",

For what its worth, I used to see this problem allot, and now I don't see it at all any more. Could it have been caused by the WoW client code (which has been updated since my opening of this ticket) and not ag_UnitFrames?