Date: 2020-06-18 05:47:20
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\SexyMap\Buttons.lua line 273:
Wrong object type for function
Debug:
[C]: GetName()
SexyMap\Buttons.lua:273:
SexyMap\Buttons.lua:268
[C]: ?
Locals:
(*temporary) =

AddOns:
Swatter, v8.2.6377 (SwimmingSeadragon)
ACP, v3.5.7
AtlasLootClassic, vv1.5.1
AtlasLootClassicData, vv1.5.1
AtlasLootClassicDungeonsAndRaids, vv1.5.1
AucAdvanced, v8.2.6430 (SwimmingSeadragon)
AucFilterBasic, v8.2.6364 (SwimmingSeadragon)
AucScanData, v8.2.6365 (SwimmingSeadragon)
AucStatHistogram, v8.2.6366 (SwimmingSeadragon)
AucStatiLevel, v8.2.6370 (SwimmingSeadragon)
AucStatPurchased, v8.2.6367 (SwimmingSeadragon)
AucStatSimple, v8.2.6399 (SwimmingSeadragon)
AucStatStdDev, v8.2.6369 (SwimmingSeadragon)
AucUtilFixAH, v8.2.6371 (SwimmingSeadragon)
AuctionDB, vv1.02.01
AutoVendor, v68-classic
BagBrother, v
Bagnon, v8.3.5
BagnonConfig, v
BeanCounter, v8.2.6434 (SwimmingSeadragon)
BetterVendorPrice, vv1.13.04
CharacterStatsClassic, v3.5.3
ClassicAuraDurations, v1.13.57
Dismounter, v1.2.1
eAlignClassic, vClassic
Enchantrix, v8.2.6428 (SwimmingSeadragon)
EnchantrixBarker, v8.2.6469 (SwimmingSeadragon)
FiveSecondRule, v1.21
GatherMate2, v1.45.5
Informant, v8.2.6374 (SwimmingSeadragon)
KuiMedia, v
KuiNameplates, v
KuiNameplatesCore, v
LeatrixMaps, v1.13.68
LeatrixPlus, v1.13.68
ModernTargetFrame, v1.6
MonkeySpeed, vv3.4.0
NugComboBar, v1.13.4
NugComboBarGUI, v
OmniCC, v8.3.5
OmniCCConfig, v
Prat30, v3.8.22
Prat30Libraries, v
Quartz, v3.5-classic-5
RangeDisplay, vv4.9.3
SexyMap, vv5-classic
SlideBar, v8.2.6375 (SwimmingSeadragon)
SLoTe, v
SpeedyAutoLoot, v2.0.27
Stubby, v8.2.6376 (SwimmingSeadragon)
WeakAuras, v2.17.8
BlizRuntimeLib_enUS v1.13.4.11304
(ck=62e)

(On WoW Classic) I get the same error all the time. I think there was another ticket or post somewhere, where the reporter was asked to turn off all the add-ons and try just SexyMap. When I only activate SexyMap this error never occurs. I tried narrowing it down, but I can't tell what is causing the error. It seems to depend on the number of add-ons loaded. The more add-ons I load the more frequent/faster this error occurs. But I couldn't pin point it to a specific add-on. quite the contrary I can recreate this problem with two disjoint sets of add-ons.