So my questions are:
Why does it pick up errors that do not appear without using BugSack?
Why does it soooo greatly impact framerate?
I had the same issue, so I loaded up TekSupport. Lo and behold, 25,000+ ADDON_ACTION_BLOCKED errors in the space of about 2 minutes. So the event handler was being called 210ish times per second, thus the frame lag. The reason it picks up the errors is that it registers said event, while other error handlers may not.
I had the same issue, so I loaded up TekSupport. Lo and behold, 25,000+ ADDON_ACTION_BLOCKED errors in the space of about 2 minutes. So the event handler was being called 210ish times per second, thus the frame lag. The reason it picks up the errors is that it registers said event, while other error handlers may not.
When exactly does that default Blizzard "Addon blocked" warning pop up then? Apparently it is unrelated to the ADDON_ACTION_BLOCKED event...
Can it be changed so that "Filter addon mistakes" will unregister BugSack from this event, because currently it makes no difference.
They won't be caught by BS/BG, since people whine about it reducing their FPS.
Maybe you should try addons that don't give you 12k errors/minute, but hey, fair enough, I'll remove the event registration from BG if the "Filter Addon Mistakes" option in BS is on.
One of these two mods, or both in combination absolutely DO cause taint or some sort. They threw up approx. 7500 errors in two days time for everything from Warmup to Nurfed Unitframes. They are picking up things that Blizzard's error warning doesn't, which to me, means it's Bugsack/Grabber. I tried running chronometer and Bugsack/grabber ONLY, and got 17 errors for the multibarleft and the shapeshiftbar(?!?!?!). Neither addon has jack to do with either of those things in game. So, IMO, the errors are being caused by those two bug mods. I get no more errors without them running.
BugGrabber and BugSack do not taint anything, but i tried tracking down those taints as well. And i _think_ something in the AceComm Library does it, but i am not sure yet. Will try to track it down further.
They won't be caught by BS/BG, since people whine about it reducing their FPS.
Maybe you should try addons that don't give you 12k errors/minute, but hey, fair enough, I'll remove the event registration from BG if the "Filter Addon Mistakes" option in BS is on.
Well, since nixing BugSack/Grabber, I get no more errors. And I still use a couple Ace2 mods that use Ace Comm. I've moved to Improved Error Frame now and don't have a problem.
No, it'll list up to the number your tell it to (I think up to 5000 or so, 100 by default). It just condenses the view so you only have one of each type.
Interesting that BG/BS is causing so many problems. I've been having framerate issues of late, I wrote it off to being agUF or BT3 and swallowed it. I'll have to take a look and see if disabling these will help any ^^.
Would be great,
last week i got the addon blocked when i pressed the "duel" button on a fellow hordie.. i figured bugsack would have caught that one.
Quote from FlareCDE »
No, it'll list up to the number your tell it to (I think up to 5000 or so, 100 by default). It just condenses the view so you only have one of each type.
Hmm. ill have to look into it later..
on hover i get like:
130x CT_Core, something hide frame
126x CT_Core, something show frame
23x Yata, element fire
15x Yata, element earth
17x Yata, element air
Always no more than 5 lines condensed. even though there may be more types of errors. (some other ace2 for instance)
anyway, i'll check my settings,, its possible i missed one that allows it to show more than 5 lines in the popup.
[2007/01/04 12:48:40-45-x1]: !BugGrabber\BugGrabber.lua:473: bad argument #3 to 'format' (string expected, got no value)
!BugGrabber\BugGrabber.lua:473: in function <Interface\AddOns\!BugGrabber\BugGrabber.lua:454>
---
With r23215 upon loading into wow.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I had the same issue, so I loaded up TekSupport. Lo and behold, 25,000+ ADDON_ACTION_BLOCKED errors in the space of about 2 minutes. So the event handler was being called 210ish times per second, thus the frame lag. The reason it picks up the errors is that it registers said event, while other error handlers may not.
When exactly does that default Blizzard "Addon blocked" warning pop up then? Apparently it is unrelated to the ADDON_ACTION_BLOCKED event...
Can it be changed so that "Filter addon mistakes" will unregister BugSack from this event, because currently it makes no difference.
Will that just mean that the ADDON_ACTION_BLOCKED errors wont happen or just wont be caught by BugGrabber/BugSack?
Maybe you should try addons that don't give you 12k errors/minute, but hey, fair enough, I'll remove the event registration from BG if the "Filter Addon Mistakes" option in BS is on.
namely swatter and VFL?
Cheers.
It seems that isn't working :/
i notice it counts the errors, but only 5 types.
Interesting that BG/BS is causing so many problems. I've been having framerate issues of late, I wrote it off to being agUF or BT3 and swallowed it. I'll have to take a look and see if disabling these will help any ^^.
Would be great,
last week i got the addon blocked when i pressed the "duel" button on a fellow hordie.. i figured bugsack would have caught that one.
Hmm. ill have to look into it later..
on hover i get like:
Always no more than 5 lines condensed. even though there may be more types of errors. (some other ace2 for instance)
anyway, i'll check my settings,, its possible i missed one that allows it to show more than 5 lines in the popup.
I just did, hence my previous post.
And no, a maximum of 5 errors will be shown in the *tooltip*. If you want to see more errors, you'll have to open the bug sack.
!BugGrabber\BugGrabber.lua:473: in function <Interface\AddOns\!BugGrabber\BugGrabber.lua:454>
---
With r23215 upon loading into wow.