Vector-: ok, that helped a bunch. Seems you had 2200 errors caught.... Guess WoW blew up on the size of the table inside (2.3M of errors might do that ;-) ). That it happened is my fault, I didn't put in a limit on the size of the sack.
I've now put a limit on the nr of errors saved, it's configurable per the BugSack menu (or slash commands). I started WoW using this limit with your SavedVariables and it didn't crash for me, but that might also be because I have more memory available than you.
Nightdew, I suspect this was also the cause of your crashes. See below for a useful development toggle.
In any case, if people are still experiencing crashes after updating the SVN, I'd still like to take a look at the SavedVariables\!BugGrabber.lua, so please post it in that case.
Furthermore, I've added a toggle that tells BugGrabber to put the errors in a temporary database that is not saved to disk. This is probably handy when developing addons (because you regularly expect and fix the errors that are popping up, and aren't interested in keeping those for later analysis).
LordRhys, are you sure you are running the latest FuBar-2.0 from the SVN? I did fix the category just now, so maybe it'll show up now...
Again, thanks for all the testing so far everyone!
- Registered User
Member for 14 years, 4 months, and 24 days
Last active Fri, Oct, 4 2013 14:29:42
- 0 Followers
- 61 Total Posts
- 0 Thanks
Aug 6, 2006OK, I fixed a few of the bugs, most notably the lag, on the SVN; but note that showing all errors in the current frame will probably not work, I need to rework the whole frame unfortunately. The copy & paste problem is fixed now though. Furthermore I fixed the nr of errors showing up on the FuBar plugin.Posted in: General AddOns
dsdranor: I forgot to add your icon earlier, oops. It's in there now, many thanks!
teedog: I tested BulkMail but I didn't get any errors, so I can't reproduce your problem. Care to paste the errors or tell me how to reproduce them?
Jayblah: I just fixed an error in the FuBar plugin that did that, can you update and retry?
Also if anyone can reproduce the WoW crash, please attach your !BugGrabber.lua and BugSack.lua savedvariables files, so that I can work around the crash.
Aug 5, 2006Teedog: I'll install bulkmail and see what's happening. I don't see the FPS issue, but I can take a look at the code and guess what's inefficient, no promises there though.Posted in: General AddOns
Azgrim: this definitely isn't happening for me, I developed it using /console reloadui a lot. I need you to check which combo of addons is making that happen for you, there's no way for me to see what is going on otherwise.
Thanks for testing so far, I noticed a bug in the FuBar plugin myself - it doesn't display the right nr of errors. I'll fix it sometime this weekend but I won't have much WoW time so it might be until Monday.
Aug 4, 2006OK, the rewrite is up on the svn now. I'm pretty confident that this version is much more robust, but hey, prove me wrong :)Posted in: General AddOns
Gamefaq: that's the same error Jayblah reported, it should not occur using the new version anymore. If it does please let me know.
Please post any other oddities/errors here also.
Aug 4, 2006I'm nearly done rewriting both addons to split out the error catching part into !BugGrabber, so that that doesn't depend on Ace2 anymore. That way if something Ace2 related goes haywire, bugs don't disappear. It should make things a little bit more reliable. Jayblah, theondry: the rewrite should also fix those errors.Posted in: General AddOns
I think I can get it done this evening, so bear with me for little while longer...
Aug 3, 2006I've come to the conclusion that it's better off as !BugGrabber -- while it doesn't work for everyone obviously it worked for enough people, so we'll just have to deal with the '!'.Posted in: General AddOns
Rename is happening tonight when I can actually test things.
maia: LoadWith: Ace2, Ace doesn't make sense for non-developers either because they won't have those addons anyway (at least, when all Ace using addons have been converted). Besides I'm not sure what WoW does when an addon wants to LoadWith an addon that's not present; I'll test that tonight.
dsDranor: cool! The icon was the result of my 'pick a WoW icon that looks like a sack in about 1 minute' graphics skillz; and it showed. New icon going in tonight as well.
theondry: yes, I merged it to the trunk to get some more people to test it (and look, it worked! ;-) )
Aug 2, 2006It's been renamed to BugGrabber because it seems that lots of computers don't load addons in alphabetical order anyway, so the '!' thingy was only annoying. Although I'm considering reverting that change because it didn't hurt anyone either, and it helped at least one class of people.Posted in: General AddOns
In any case, I'm told the only way to make sure it's loaded early is to add a '## LoadWith: SomeEarlyAddon' line to the .toc where you need to determine 'SomeEarlyAddon' yourself unfortunately.
I'd love to have 'LoadWith: FrameXML' working; if someone can make a post to that effect on the US WoW UI forums stating that it might help in this case, maybe slouken will consider it.
Jul 28, 2006Now on the SVN in /trunk: a rewritten !BugGrabber / BugSack.Posted in: General AddOns
Changes that I made:
- BugSack now unconditionally depends on !BugGrabber. This is because I changed !BugGrabber to grab the bugs; BugSack is now only a shell that displays the errors. I did this because errors in Ace2 libraries tended to keel over other Ace2 addons. Since BugSack is now an Ace2 addon, that meant errors got lost. The new BugGrabber should print errors to the chat frame if BugSack is dead, which prevents errors from getting lost alltogether.
- Added a new FuBar-2.0 plugin that'll show the current nr of errors.
Changes kergoth made:
- Added a backtrace to errors; now you can see the whole call stack
- Prettified the error message a little (no more Interface\ clutter)
Any and all bug reports appreciated.
- To post a comment, please login or register a new account.