I just reinstalled WoW...
[2009/02/19 12:48:07-8-x1]: AutoBar-v3.00.08.15 beta.737\AutoBarClassBar.lua:221: attempt to index field '?' (a nil value)...
How did you go about installing it? 737 is from Jan 20. It is now Feb 20, and a patch later as well I think... (and 748 is the latest beta).
Apologies if this has been asked before, searched here and on Google but didn't turn up anything.
Created a custom 'pick lock' category for use across characters, wanting to include both the rogue 'pick lock' and blacksmithing skeleton keys.
Discovered that although you can put the skeleton keys into a custom category from the keyring, they aren't selectable for as long as the keys remain stored there. Put them into a standard inventory bag and they're fine for use.
Is this known and expected behaviour? If so, np, i'll simply leave my keys in my bag rather than on the keyring, but if possible I'd prefer to save the bagspace! :)
... and most Northrend quest items are missing from the quest item bar.
Feh.
Get the newest LibPT release and replace existing PT folders in the Autobar folder.
If you have anyother Addon installed using PT and loading before Autobar, do the same there.
After that Northrend quest items come back to Autobar.
For some reason autobar has started racking up huge amounts of garbage memory lately.
I run disembeded (even ripped out LDB-1.1 while testing)
Im getting huge memory climbs in very short time (5-10MB in a matter of minutes)
Seems to be especially bad when im swapping gears (using outfitter).
Initial memory sits at 2.7MB and in just a few min (2-3) its shooting well over 10MB, it goes away properly on gabagedump, but between automaric dumps it started to race a bit out of hand.
For some reason autobar has started racking up huge amounts of garbage memory lately.
I run disembeded (even ripped out LDB-1.1 while testing)
Im getting huge memory climbs in very short time (5-10MB in a matter of minutes)
Seems to be especially bad when im swapping gears (using outfitter).
Initial memory sits at 2.7MB and in just a few min (2-3) its shooting well over 10MB, it goes away properly on gabagedump, but between automaric dumps it started to race a bit out of hand.
What does lately mean? As in, can you go back to a version that does not? I assume you have disabled all other mods when you get these results.
I run fully disembeded so no libs are present in the autobar folder and with that it shouldn't be possible for AB to get blamed for other addons usage, or have i misunderstood something here?
And if its other libs being used then the one getting the blame should be Altoholic (thats not fully disembeded) being above AB in the list.
I haven't really been testing old versions, i just noticed a while back that the amount of "garbage" memory on AB was running wild since my UI was suddenly rushing out of hand with 120+MB even with recount of.
Swatter or whatever you are using is totally useless for me. It lists all your mods instead of doing a good job showing the actual bug. It is literally the spawn of satan and you can google these threads for proof. Install buggrabber and bugsack. If you get an error use bugsack to copy and paste it.
Also, please go back and edit out that gigantic message. Just so you know, your bug has nothing to do with AutoBar. The link has instructions for how to find the broken mod.
I run fully disembeded so no libs are present in the autobar folder and with that it shouldn't be possible for AB to get blamed for other addons usage, or have i misunderstood something here?...
I believe you only misunderstood the part about having only AutoBar enabled. If you run with the latest version, and it alone, but get massive memory usage like that then post and I will take a look. Unless you run with only AutoBar, then the chances of me reproducing your environment and thus the error is zero. Oh, you can also have your memory mod running. Which are you using btw?
Toadkiller,
I haven't seen much activity w/ AutoBar in a while. I was wondering if you planned on updating it for WoW 3.1? I don't know if there were changes that damaged it, but at least the toc?
If you're no longer working on it, that'd be nice to know also.
There's a beta for 3.1 on the curse site. I had problems with the latest release version, and the curse client wouldn't show me the beta, so I had to download it manually, but at least autobar is working again. I didn't check the toc because I have other stuff that requires me to "load outdated addons", but that's really a minor thing.
I also have had the no autobars problems since 3.1.1 here is the Bug sack with the Feb version of Autobar
2009/04/22 12:43:28-1-x1]: LibBabble-Zone-3.0-?:14: Cannot find a library instance of "LibBabble-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
LibBabble-Zone-3.0-?:14: in main chunk
[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.735\Core.lua:626: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.735\Core.lua:626: in main chunk
--[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\AutoBarSearch.lua:18: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.737\AutoBarSearch.lua:18: in main chunk
---[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\AutoBarCategory.lua:39: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.737\AutoBarCategory.lua:39: in main chunk
---[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:274: attempt to index global 'AutoBarCategory' (a nil value)
AceAddon-2.0-91094 (AutoBar):541: in function <...ce\AddOns\AutoBar\libs\AceAddon-2.0\AceAddon-2.0.lua:518>
<in C code>: ?
AceEvent-2.0-91091 (AutoBar):298: in function `TriggerEvent'
AceEvent-2.0-91091 (AutoBar):910: in function <...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:903>
---[2009/04/22 12:43:29-1-x1]: AceOO-2.0-91091 (AutoBar):734: AceComm-2.0: AceComm-2.0 requires AceEvent-2.0
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:43:29-1-x1]: AceComm-2.0-91091:2241: attempt to call method 'UnregisterAllComms' (a nil value)
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:43:30-1-x1]: FuBar_FishingBuddyFu-2.2c\FuBar_FishingBuddy.lua:16: attempt to call field 'Color' (a nil value)
---[2009/04/22 12:43:36-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:316: Usage: RegisterCallback("eventname", "methodname"): 'methodname' - method 'LIBKEYBOUND_ENABLED' not found on self.
AceAddon-2.0-91096:983: in function <...\DailyQuestViewer\libs\AceAddon-2.0\AceAddon-2.0.lua:976>
<in C code>: ?
AceEvent-2.0-91091 (AutoBar):260: in function `TriggerEvent'
AceEvent-2.0-91091 (AutoBar):910: in function <...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:903>
---[2009/04/22 12:43:37-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:498: attempt to index field 'UpdateCategories' (a nil value)
AutoBar-v3.00.08.15 beta.737\Core.lua:248: in function <Interface\AddOns\AutoBar\Core.lua:247>
---[2009/04/22 12:43:37-1-x2]: AutoBar-v3.00.08.15 beta.737\Core.lua:248: attempt to call field '?' (a nil value)
---
and here is the same thing with the 3.1 beta from curse this update does get me back my autobars but since it is still tossing up an error in something called acecomm 2.0 I thought I better report it
[2009/04/22 12:54:08-2-x1]: AceOO-2.0-91091 (AutoBar):734: AceComm-2.0: AceComm-2.0 requires AceEvent-2.0
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:54:08-2-x1]: AceComm-2.0-91091:2241: attempt to call method 'UnregisterAllComms' (a nil value)
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:54:08-2-x1]: FuBar_FishingBuddyFu-2.2c\FuBar_FishingBuddy.lua:16: attempt to call field 'Color' (a nil value)
---
I know the Fishing buddy stuff has nothing to do with you but I include it for completeness
I just wanted to say thank you for keeping this up to date, and that it is working great for me.
The one question I have is if you have an ETA when you plan on adding some of the new items from 3.1 to the bar like Black Jelly or the Inscribed Kirin Tor rings?
Just to say - same problem. Logged on last night updated to new version (not played for a week or 2 ) All fine. Then Blizard announced a server restart. Today get the same lib babble messages as Winshadow - no autobar now in 3.1.1
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
How did you go about installing it? 737 is from Jan 20. It is now Feb 20, and a patch later as well I think... (and 748 is the latest beta).
Created a custom 'pick lock' category for use across characters, wanting to include both the rogue 'pick lock' and blacksmithing skeleton keys.
Discovered that although you can put the skeleton keys into a custom category from the keyring, they aren't selectable for as long as the keys remain stored there. Put them into a standard inventory bag and they're fine for use.
Is this known and expected behaviour? If so, np, i'll simply leave my keys in my bag rather than on the keyring, but if possible I'd prefer to save the bagspace! :)
Get the newest LibPT release and replace existing PT folders in the Autobar folder.
If you have anyother Addon installed using PT and loading before Autobar, do the same there.
After that Northrend quest items come back to Autobar.
This kind of needs a custom button that knows where to look for keys. The keyring is not looked at right now for items.
I run disembeded (even ripped out LDB-1.1 while testing)
Im getting huge memory climbs in very short time (5-10MB in a matter of minutes)
Seems to be especially bad when im swapping gears (using outfitter).
Initial memory sits at 2.7MB and in just a few min (2-3) its shooting well over 10MB, it goes away properly on gabagedump, but between automaric dumps it started to race a bit out of hand.
Same here.
What does lately mean? As in, can you go back to a version that does not? I assume you have disabled all other mods when you get these results.
I run fully disembeded so no libs are present in the autobar folder and with that it shouldn't be possible for AB to get blamed for other addons usage, or have i misunderstood something here?
And if its other libs being used then the one getting the blame should be Altoholic (thats not fully disembeded) being above AB in the list.
I haven't really been testing old versions, i just noticed a while back that the amount of "garbage" memory on AB was running wild since my UI was suddenly rushing out of hand with 120+MB even with recount of.
Im very well aware of that, that's one of the main reasons i run my UI disembedded, so i get accurate values from the addons.
Date: 2009-03-21 10:35:47
ID: 4
Error occured in: Global
Count: 70
Message: ...bs\SpecialEvents-Aura-2.0\SpecialEvents-Aura-2.0.lua line 281:
attempt to call upvalue 'GetPlayerBuff' (a nil value)
Debug:
...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:299: TriggerEvent()
...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:910:
...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:903
AddOns:
Afflicted, v$Revision: 943 $
ArenaHistorian, v$Revision: 971 $
AutoBar, vv3.00.08.15 beta
Babylonian, v5.1.DEV.130
Bagnon, v1.6.10
BagnonForever, v1.1.1
BagnonTooltips, v
Buffalo, v
Cartographer, v2.0
CartographerBattlegrounds, v2.0
CartographerCoordinates, v2.0
CartographerFoglight, v2.0
CartographerGroupColors, v2.0
CartographerGuildPositions, v2.0
CartographerInstanceLoot, v2.0
CartographerInstanceMaps, v2.0
CartographerInstanceNotes, v2.0
CartographerLookNFeel, v2.0
CartographerNotes, v2.0
CartographerPOI, v2.0
CartographerProfessions, v2.0
CartographerWaypoints, v2.0
CartographerZoneInfo, v2.0
CCTimer, v3.0
Chatter, v1.0
Configator, v5.1.DEV.160
CurseProfiler, v
DBMCore, v
Decursive, v2.4_beta_3_STABLE
Dominos, v1.8.3
DominosBuff, v
DominosCast, v
DominosRoll, v
DominosXP, v
EQCompare, v2.0
FruityLoots, v2.0
Gatherer, v3.1.11
GathererDBWowhead, v1.0.%date%
Gladius, vr23
Grid, v1.30000.2009021101
GridAlert, v$Rev: 72732 $
GridAutoFrameSize, v2.3.3
GridLayoutForHealers, v0.2
GridStatusHealingReduced, v3.0.3.23
GridStatusHots, v3.1
GridStatusIncomingHeals, v
GrimReaper, v2.0 $Revision: 59 $
ItemRack, v
Koordinator, v3.27
LibItemVendorPricesDB2SavedVariables, vn/a
MikScrollingBattleText, v5.3.36
MobHealth, v3.3
Omen, v3.0.6
OmniCC, v2.3.1
oRA2, v2.0.$Revision: 628 $
PallyPower, vv3.0.17-release
Postal, v3.1.0
PowerAuras, v2.6.0
QualityID, v3.05.@project-revision@
Quartz, v1.0
QuartzBuff, v1.0
QuartzFlight, v1.0
QuartzFocus, v1.0
QuartzGCD, v1.0
QuartzInterrupt, v1.0
QuartzLatency, v1.0
QuartzMirror, v1.0
QuartzPet, v1.0
QuartzPlayer, v1.0
QuartzRange, v1.0
QuartzSwing, v1.0
QuartzTarget, v1.0
QuartzTimer, v1.0
QuartzTradeskill, v1.0
RaidCooldowns, v
RaidCooldownsDisplay, v
RatingBuster, v
Recount, v
TinyTip, v0.3-Beta
VendorValues, v5.0.2
WinterTime, v1.63
XPerl, v3.0.2a
XPerlArcaneBar, v
XPerlParty, v
XPerlPartyPet, v
XPerlPlayer, v
XPerlPlayerBuffs, v
XPerlPlayerPet, v
XPerlRaidAdmin, v
XPerlRaidFrames, v
XPerlRaidHelper, v
XPerlRaidMonitor, v
XPerlRaidPets, v
XPerlTarget, v
XPerlTargetTarget, v
(ck=8d3)
Please follow all instructions here exactly as they are stated: http://code.google.com/p/autobar/wiki/ErrorsBugs
Swatter or whatever you are using is totally useless for me. It lists all your mods instead of doing a good job showing the actual bug. It is literally the spawn of satan and you can google these threads for proof. Install buggrabber and bugsack. If you get an error use bugsack to copy and paste it.
Also, please go back and edit out that gigantic message. Just so you know, your bug has nothing to do with AutoBar. The link has instructions for how to find the broken mod.
I believe you only misunderstood the part about having only AutoBar enabled. If you run with the latest version, and it alone, but get massive memory usage like that then post and I will take a look. Unless you run with only AutoBar, then the chances of me reproducing your environment and thus the error is zero. Oh, you can also have your memory mod running. Which are you using btw?
I haven't seen much activity w/ AutoBar in a while. I was wondering if you planned on updating it for WoW 3.1? I don't know if there were changes that damaged it, but at least the toc?
If you're no longer working on it, that'd be nice to know also.
thanks
-
View User Profile
-
View Posts
-
Send Message
Curse Premium2009/04/22 12:43:28-1-x1]: LibBabble-Zone-3.0-?:14: Cannot find a library instance of "LibBabble-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
LibBabble-Zone-3.0-?:14: in main chunk
[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.735\Core.lua:626: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.735\Core.lua:626: in main chunk
--[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\AutoBarSearch.lua:18: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.737\AutoBarSearch.lua:18: in main chunk
---[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\AutoBarCategory.lua:39: Cannot find a library instance of "LibBabble-Zone-3.0".
SlideBar-6\Support\LibRevision.lua:47: in function `LibStub'
AutoBar-v3.00.08.15 beta.737\AutoBarCategory.lua:39: in main chunk
---[2009/04/22 12:43:28-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:274: attempt to index global 'AutoBarCategory' (a nil value)
AceAddon-2.0-91094 (AutoBar):541: in function <...ce\AddOns\AutoBar\libs\AceAddon-2.0\AceAddon-2.0.lua:518>
<in C code>: ?
AceEvent-2.0-91091 (AutoBar):298: in function `TriggerEvent'
AceEvent-2.0-91091 (AutoBar):910: in function <...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:903>
---[2009/04/22 12:43:29-1-x1]: AceOO-2.0-91091 (AutoBar):734: AceComm-2.0: AceComm-2.0 requires AceEvent-2.0
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:43:29-1-x1]: AceComm-2.0-91091:2241: attempt to call method 'UnregisterAllComms' (a nil value)
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:43:30-1-x1]: FuBar_FishingBuddyFu-2.2c\FuBar_FishingBuddy.lua:16: attempt to call field 'Color' (a nil value)
---[2009/04/22 12:43:36-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:316: Usage: RegisterCallback("eventname", "methodname"): 'methodname' - method 'LIBKEYBOUND_ENABLED' not found on self.
AceAddon-2.0-91096:983: in function <...\DailyQuestViewer\libs\AceAddon-2.0\AceAddon-2.0.lua:976>
<in C code>: ?
AceEvent-2.0-91091 (AutoBar):260: in function `TriggerEvent'
AceEvent-2.0-91091 (AutoBar):910: in function <...ce\AddOns\AutoBar\libs\AceEvent-2.0\AceEvent-2.0.lua:903>
---[2009/04/22 12:43:37-1-x1]: AutoBar-v3.00.08.15 beta.737\Core.lua:498: attempt to index field 'UpdateCategories' (a nil value)
AutoBar-v3.00.08.15 beta.737\Core.lua:248: in function <Interface\AddOns\AutoBar\Core.lua:247>
---[2009/04/22 12:43:37-1-x2]: AutoBar-v3.00.08.15 beta.737\Core.lua:248: attempt to call field '?' (a nil value)
---
and here is the same thing with the 3.1 beta from curse this update does get me back my autobars but since it is still tossing up an error in something called acecomm 2.0 I thought I better report it
[2009/04/22 12:54:08-2-x1]: AceOO-2.0-91091 (AutoBar):734: AceComm-2.0: AceComm-2.0 requires AceEvent-2.0
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:54:08-2-x1]: AceComm-2.0-91091:2241: attempt to call method 'UnregisterAllComms' (a nil value)
AceComm-2.0-91091:2339: in main chunk
---[2009/04/22 12:54:08-2-x1]: FuBar_FishingBuddyFu-2.2c\FuBar_FishingBuddy.lua:16: attempt to call field 'Color' (a nil value)
---
I know the Fishing buddy stuff has nothing to do with you but I include it for completeness
The one question I have is if you have an ETA when you plan on adding some of the new items from 3.1 to the bar like Black Jelly or the Inscribed Kirin Tor rings?