Authors CurseForge

OK, 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.

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.

Quote from Fritti »

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?

The error in BulkMail was fixed in the last update. If you still want to reproduce it try using a previous revision and simply use it to mail some items.

I did indeed save my old faulty saved variable files, or rather I hadn't clared my trash bin since then, so I was able to restore them

They're attached, and it bears noting that with the current SVN version, these saved variables files crash on loading for me, rather than just on logging out or reloading UI

Otherwise, the current SVN version is working beautifully for me however

Last night i was coding and usinng BG/BS. I was having bugs and it was all shown to me clearly. However, at some point reloading UI started crashing WoW.. so i rebooted thinking maybe some mem leak or wtf ever. Nope, it didnt help. I cleared the saved vars for BG and all is good, now.

I d/l this and installed it, seems to be working ok except it doen't show up in my Fubar2 bar, and is not listed in any category to toggle on or off.

Quote from LordRhys »

I d/l this and installed it, seems to be working ok except it doen't show up in my Fubar2 bar, and is not listed in any category to toggle on or off.

It never showed in my fubar till I installled fubar 2.0. Since then it hasnt missed a beat.

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!

I'll do svn updates when I get home from work in a couple hours and let you know how it goes.

Updated to most recent SVN... I cannot log into Wow... load bar only gets half way and locks up.
Rolling back and going update by update... when I update !BugGrabber is what is causing the freeze. I have made sure both Bug Sack and !BugGrabber are the most recent, I still have to roll back !BugGrabber.

Otherwise, its been running fine. this issue started occuring yesterday when I did my typical SVN Update *

Thanks

I am also having major problems with !BugGrabber. Am currently using the most recent SVN versions of !BugGrabber, BugSack, and FuBar.

About 2/3 of the time when mousing over the BugSack icon on FuBar, WoW freezes up. I can move the mouse cursor around, and I can alt-tab out, but that's it. Task Manager shows WoW using 80-100 % CPU. The problem does not resolve itself, and I have to kill the process.

Also, several times now I've had WoW crash at apparently random times, and in the error report, !BugGrabber.lua is listed in the memory dump section.

Edit: I suppose I should add that the freezing does happen when only !BugGrabber, BugSack, and FuBar are enabled, and it does happen after deleting saved variables. As the crashing is random, I can't really test, but I'm guessing it'd happen under the same conditions.

Lewzephyr: someone else reported the same problem also. Can you send me your SavedVariables\!BugGrabber.lua and SavedVariables\BugSack.lua by PM (or attach them here) ? I've got one set that makes WoW crash but it won't hurt to have more. Furthermore if you delete those I think the problem will go away.

Phanx: that's also a serious problem. What other addons do you have installed? What are the last errors as shown by BugSack? You mention that it also happens without SavedVariables, but without any errors having been reported?

I will test today to see whether I can fix the crash on login.

I have... a lot of mods. Around 150 installed, anywhere from 60-100 enabled depending on which character I'm on, so I'll spare you a full list. Unless you really want one. :P

However, when only !BugGrabber, BugSack, and FuBar are enabled, it does happen. I will test and see if it happens without FuBar enabled... although since it happens when I mouseover the icon on FuBar, I'm guessing it won't. We'll see.

Yep, happens without any errors in the database at all. At least, I'm pretty sure there aren't any - I'd just wiped the saved variables file, and didn't hear the little audio alert between the time I logged in and the time I moused over the icon and froze. I'll do more testing and see if I can get something to throw an error, and see what happens if I mouseover the icon then.

with the latest on SVN I'm still not getting it to show up on FuBar, doesn't show up in any of the category lists to check on or off either. I'm using FuBar2.

I've put up a new version on the SVN that includes more loadtime checks, which should guard against load time errors in !BugGrabber itself. Unfortunately I haven't yet been able to reproduce the reported crashes so I'm still unclear as to what's causing it. Please keep sending me your SavedVariables\!BugGrabber.lua / SavedVariables\BugSack.lua files if you encounter these kinds of problems. It might also be worth checking out whether enabling only !BugGrabber and disabling BugSack fixes your problem.

I've also done the following in this version:
- tweaked the reporting of load time errors so that BugSack will catch all load time errors if it's enabled
- improved the frame somewhat by making it a bit bigger, making sure it only shows one error at a time and adding first/last/next/prev buttons to go through the list of errors
- the FuBar plugin now shows only the first line of errors in it's tooltip, and the tooltip is detachable and clickable to show specific errors

Phanx: ok, that's clear. Unfortunately I'm totally unable to reproduce it (of course). But check out the latest version, I've put some more checks in that might fix things (I hope). If you do find a way to reproduce it, let me know.

LordRhys: there's a small buglet in FuBar-2.0 right now with the 'development tools' category, but it shows up for me in the 'Others' category. Please make sure you run the latest FuBar2 along with all the latest external libraries.

All comments appreciated as always.

With latest sVN:

[18:43-42]: BugSack\BugSackFu.lua:34: FuBarPlugin-2.0: You must provide self.title or self.name
<evaluated>: in function `error'
AceLibrary\AceLibrary.lua:106: in function <...nterface\AddOns\Fubar\libs\AceLibrary\AceLibrary.lua:37>
AceLibrary\AceLibrary.lua:121: in function `assert'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:84: in function `GetTitle'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:298: in function `SetIcon'
BugSack\BugSackFu.lua:34: in function `OnTextUpdate'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:161: in function `UpdateText'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:146: in function `UpdateDisplay'
BugSack\BugSack.lua:449: in function `OnError'
BugSack\BugSack.lua:220: in function `OnInitialize'
AceAddon-2.0\AceAddon-2.0.lua:215: in function `InitializeAddon'
AceAddon-2.0\AceAddon-2.0.lua:110: in function `obj_method'
AceEvent-2.0\AceEvent-2.0.lua:174: in function `TriggerEvent'
AceEvent-2.0\AceEvent-2.0.lua:842: in function <...face\AddOns\Fubar\libs\AceEvent-2.0\AceEvent-2.0.lua:834>

Thanks for the update.... I have downloaded the most recent SVN just a few min ago... Game loads up with no issues.

Alright. Updated to the latest SVN versions, and the freeze on mouseover isn't happening anymore. Hopefully the random crash is also fixed! :P

Also, I'm getting the same error as Gamefaq, but with different line numbers:

BugSack\BugSackFu.lua:34: FuBarPlugin-2.0: You must provide self.title or self.name
<evaluated>: in function `error'
AceLibrary\AceLibrary.lua:106: in function <...nterface\AddOns\FuBar\libs\AceLibrary\AceLibrary.lua:37>
AceLibrary\AceLibrary.lua:121: in function `assert'
FuBarPlugin\FuBarPlugin-2.0.lua:84: in function `GetTitle'
FuBarPlugin\FuBarPlugin-2.0.lua:305: in function `SetIcon'
BugSack\BugSackFu.lua:34: in function `OnTextUpdate'
FuBarPlugin\FuBarPlugin-2.0.lua:164: in function `UpdateText'
FuBarPlugin\FuBarPlugin-2.0.lua:149: in function `UpdateDisplay'
BugSack\BugSack.lua:449: in function `OnError'
BugSack\BugSack.lua:220: in function `OnInitialize'
AceAddon-2.0\AceAddon-2.0.lua:215: in function `InitializeAddon'
AceAddon-2.0\AceAddon-2.0.lua:110: in function `obj_method'
AceEvent-2.0\AceEvent-2.0.lua:213: in function `TriggerEvent'
AceEvent-2.0\AceEvent-2.0.lua:919: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:911>

That's good news! I know why that error is happening, I can probably fix it tonight. I just learned that FuBar-2.0 plugins don't even have to depend on FuBar so I needed to rewrite a bit of it in any case.

Last SVN as of two minutes ago. The first error may not be generated by bugsack, but it looked similar to the errors above this post so I thought I might post it.

Edit: In fact the errors are exactly the same. No point in me posting the same bugs :)


Is it me or have errors got a whole lot more complex?

Quote from scae »

Is it me or have errors got a whole lot more complex?

With the advent of embeded librarys, some bugs were getting blamed on Addons that weren't causeing them.

For example, if a mod uses some part of AceEvent improperly, AceEvent would get the blame, and it would be very hard to know what was wrong in the mod that *actually* caused it.

BugSack was changed in response to show more information so we can track down and squash real bugs :)