Thread Tools Display Modes
12-19-06, 05:38 AM   #1
greenstpne
A Murloc Raider
Join Date: Dec 2006
Posts: 6
Ctmod errors - *shown with bugsack.

[1] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup7:Show()'.\n<in C code>: in function `Show'\nCT_RaidAssist\\CT_RaidAssist.lua:2473: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[2] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup8:Show()'.\n<in C code>: in function `Show'\nCT_RaidAssist\\CT_RaidAssist.lua:2473: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[3] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAMTGroup:Hide()'.\n<in C code>: in function `Hide'\nCT_RaidAssist\\CT_RaidAssist.lua:2493: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[4] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAMTGroupDrag:Hide()'.\n<in C code>: in function `Hide'\nCT_RaidAssist\\CT_RaidAssist.lua:2494: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[5] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAMTTGroup:Hide()'.\n<in C code>: in function `Hide'\nCT_RaidAssist\\CT_RaidAssist.lua:2499: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[6] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAPTGroup:Hide()'.\n<in C code>: in function `Hide'\nCT_RaidAssist\\CT_RaidAssist.lua:2518: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[7] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAPTGroupDrag:Hide()'.\n<in C code>: in function `Hide'\nCT_RaidAssist\\CT_RaidAssist.lua:2519: in function `CT_RA_UpdateRaidFrames'\nCT_RaidAssist\\CT_RaidAssist.lua:1091: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:55:16",
["session"] = 9,
["counter"] = 9,
},
[9] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_Core' tried to call the protected function 'PartyMemberFrame1:Show()'.\n<in C code>: in function `Show'\nFrameXML\\PartyMemberFrame.lua:51: in function `PartyMemberFrame_UpdateMember'\nFrameXML\\PartyMemberFrame.lua:142: in function `PartyMemberFrame_OnEvent'\n<string>:\"PartyMemberFrame1:OnEvent\":2: in function <[string \"PartyMemberFrame1:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 01:56:02",
["session"] = 9,
["counter"] = 2,
},
[132] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup3UnitButton1:SetHeight()'.\n<in C code>: in function `SetHeight'\nCT_RaidAssist\\CT_RaidAssist.lua:1633: in function `CT_RA_UpdateUnitDead'\nCT_RaidAssist\\CT_RaidAssist.lua:1354: in function `CT_RA_UpdateUnitStatus'\nCT_RaidAssist\\CT_RaidAssist.lua:2368: in function `CT_RA_UpdateGroupVisibility'\n<string>:\"CT_RAGroup3UnitButton5:OnAttributeChanged\":11: in function <[string \"CT_RAGroup3UnitButton5:OnAttributeChanged\"]:1>\n<in C code>: in function `SetAttribute'\nFrameXML\\SecureTemplates.lua:748: in function <Interface\\FrameXML\\SecureTemplates.lua:696>\nFrameXML\\SecureTemplates.lua:841: in function `SecureRaidGroupHeader_Update'\nFrameXML\\SecureTemplates.lua:582: in function `SecureRaidGroupHeader_OnEvent'\n<string>:\"CT_RAGroup3:OnEvent\":2: in function <[string \"CT_RAGroup3:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 03:03:48",
["session"] = 9,
["counter"] = 1,
},
[164] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup3UnitButton3:SetHeight()'.\n<in C code>: in function `SetHeight'\nCT_RaidAssist\\CT_RaidAssist.lua:1633: in function `CT_RA_UpdateUnitDead'\nCT_RaidAssist\\CT_RaidAssist.lua:1165: in function `CT_RA_OnEvent'\n<string>:\"CT_RAFrame:OnEvent\":2: in function <[string \"CT_RAFrame:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 03:17:27",
["session"] = 9,
["counter"] = 1,
},
[196] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup1UnitButton4:SetHeight()'.\n<in C code>: in function `SetHeight'\nCT_RaidAssist\\CT_RaidAssist.lua:1587: in function `CT_RA_UpdateUnitDead'\nCT_RaidAssist\\CT_RaidAssist.lua:1354: in function `CT_RA_UpdateUnitStatus'\nCT_RaidAssist\\CT_RaidAssist.lua:2368: in function `CT_RA_UpdateGroupVisibility'\n<string>:\"CT_RAGroup1UnitButton1:OnAttributeChanged\":11: in function <[string \"CT_RAGroup1UnitButton1:OnAttributeChanged\"]:1>\n<in C code>: in function `SetAttribute'\nFrameXML\\SecureTemplates.lua:748: in function <Interface\\FrameXML\\SecureTemplates.lua:696>\nFrameXML\\SecureTemplates.lua:841: in function `SecureRaidGroupHeader_Update'\nFrameXML\\SecureTemplates.lua:582: in function `SecureRaidGroupHeader_OnEvent'\n<string>:\"CT_RAGroup1:OnEvent\":2: in function <[string \"CT_RAGroup1:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 03:57:24",
["session"] = 9,
["counter"] = 2,
},
[228] = {
["message"] = "<event>ADDON_ACTION_BLOCKED:AddOn 'CT_RaidAssist' tried to call the protected function 'CT_RAGroup3UnitButton4:SetHeight()'.\n<in C code>: in function `SetHeight'\nCT_RaidAssist\\CT_RaidAssist.lua:1633: in function `CT_RA_UpdateUnitDead'\nCT_RaidAssist\\CT_RaidAssist.lua:1354: in function `CT_RA_UpdateUnitStatus'\nCT_RaidAssist\\CT_RaidAssist.lua:2368: in function `CT_RA_UpdateGroupVisibility'\n<string>:\"CT_RAGroup3UnitButton1:OnAttributeChanged\":11: in function <[string \"CT_RAGroup3UnitButton1:OnAttributeChanged\"]:1>\n<in C code>: in function `SetAttribute'\nFrameXML\\SecureTemplates.lua:758: in function <Interface\\FrameXML\\SecureTemplates.lua:696>\nFrameXML\\SecureTemplates.lua:841: in function `SecureRaidGroupHeader_Update'\nFrameXML\\SecureTemplates.lua:582: in function `SecureRaidGroupHeader_OnEvent'\n<string>:\"CT_RAGroup3:OnEvent\":2: in function <[string \"CT_RAGroup3:OnEvent\"]:1>\n\n ---",
["type"] = "event",
["time"] = "2006/12/19 03:57:24",
["session"] = 9,
["counter"] = 5,
},

Have 500 or so errors like that - happens whenever I go into combat - I disabled my other addons and yet this is still occurring.

Any idea why?
  Reply With Quote
12-19-06, 06:59 AM   #2
jshadoww
A Fallenroot Satyr
AddOn Author - Click to view addons
Join Date: Nov 2006
Posts: 22
I had the same problem, those errors are actually silent by default and its a different addon bringing them up, I think its used for debugging purposes. Try disabiling your addons one at a time until you don't get there error, when you find the one causing it, check to see if there is an update for it that says something about fixing an error like that.
  Reply With Quote
12-19-06, 07:24 PM   #3
greenstpne
A Murloc Raider
Join Date: Dec 2006
Posts: 6
Hmm

Well bugsack picks up all errors - meaning that these errors shouldn't be happening...I loaded up bugsack cause I was trying to find out what was lagging my system during combat and it turns out I am getting hundreds of errors. Wouldn't you think that is a problem?

Those errors are probably caused by some code thats either running in a loop calling a function no matter the state of combat or some open ended function that is called by ctmod to check the status of frames for buff updates or something...

Basically the mod is great but we have a lag cost associated with the use.
  Reply With Quote
12-19-06, 07:47 PM   #4
Zidomo
A Cliff Giant
 
Zidomo's Avatar
Join Date: Apr 2006
Posts: 76
Originally Posted by jshadoww
I had the same problem, those errors are actually silent by default and its a different addon bringing them up, I think its used for debugging purposes. Try disabiling your addons one at a time until you don't get there error, when you find the one causing it, check to see if there is an update for it that says something about fixing an error like that.
No, its not another addon necessarily causing them. Its mods not designed 100% properly for the patch that is the root cause of them. The CT mod author (Cide)has admitted that the CT mods (improperly) taint frames (I've already posted in the main CTMod 2.0 Bugs thread about them). Consequently, those errors will occur if you have any other mod trying to (safely or not) use those frames.

There are ways around frame tainting to become 100% compliant with the patch, but some mods (such as CT) aren't doing it.

On the other hand, if a mod going nuts tainting frames/calling protected functions (like CT mods are) are not interfering with other mods you may have installed, it may not be a gigantic issue. But those who like to find bugs with BugGrabber/BugSack or similar mods will have a tougher time trying to dig through all those ADDON_ACTION_BLOCKED errors to find other mod errors.
  Reply With Quote
12-21-06, 12:51 AM   #5
Cide
Swedeheart
AddOn Author - Click to view addons
Join Date: Jan 2005
Posts: 96
Originally Posted by Zidomo
No, its not another addon necessarily causing them. Its mods not designed 100% properly for the patch that is the root cause of them. The CT mod author (Cide)has admitted that the CT mods (improperly) taint frames (I've already posted in the main CTMod 2.0 Bugs thread about them). Consequently, those errors will occur if you have any other mod trying to (safely or not) use those frames.

There are ways around frame tainting to become 100% compliant with the patch, but some mods (such as CT) aren't doing it.

On the other hand, if a mod going nuts tainting frames/calling protected functions (like CT mods are) are not interfering with other mods you may have installed, it may not be a gigantic issue. But those who like to find bugs with BugGrabber/BugSack or similar mods will have a tougher time trying to dig through all those ADDON_ACTION_BLOCKED errors to find other mod errors.
That's not what I said at all. Taint is not avoidable at all times. The only reason this "problem" even exists is because BugSack is logging it by default, which it definitely shouldn't.
__________________
CTMod Developer
  Reply With Quote
12-21-06, 01:41 AM   #6
Dridzt
A Pyroguard Emberseer
 
Dridzt's Avatar
AddOn Author - Click to view addons
Join Date: Nov 2005
Posts: 1,359
Bugsack has a setting to filter errors related to ADDON_BLOCKED and ADDON_FORBIDDEN messages (look at advanced from right-click menu)
but that doesn't mean those errors stop happening because you don't see them.

ActionBlocked by Laric and similar addons also report them.

It also doesn't mean that these type of errors don't bog down your system and killing your fps especially in a raiding environment.

Hiding them under a carpet is not really a solution,
that we can live with them until a more robust implementation is available goes without saying.

All the work done to have functional raidframes is very much appreciated.
  Reply With Quote
12-24-06, 01:58 AM   #7
greenstpne
A Murloc Raider
Join Date: Dec 2006
Posts: 6
hmm

Originally Posted by Cide
That's not what I said at all. Taint is not avoidable at all times. The only reason this "problem" even exists is because BugSack is logging it by default, which it definitely shouldn't.
Well the problem isn't bugsack Cide, its working properly, maybe too well...

The fact is the errors I am seeing are also leading to the "target" frame being locked out during combat.

How to test:
Load up ctmod/ctraid - dont load any other addons except bugsack or laricactionblocked.

Do the following:

1. Aggro a mob - start fighting...
2. In middle of fight aggro another mob...
3. Kill first mob.
4. Look for frame of second mob...you may or may not have it.

If you look at the errors shown in bugsack during this fight you see they are all errors dealing with "target of target" or targeting during combat.

Again ctmod and ctraid are great addons to be sure - not knocking them at all - but the errors do lead to lag and as someone said pushing them under a rug won't resolve them - you are just making it more difficult to use the addon and fix proper bugs.

Last edited by greenstpne : 12-24-06 at 02:00 AM.
  Reply With Quote
01-07-07, 03:36 AM   #8
Cordelia
A Defias Bandit
Join Date: Aug 2006
Posts: 3
The problem with this approach is that, as far as I can see, ADDON_ACTION_BLOCKED and ADDON_FORBIDDEN messages are linked to that annoying UI window that pops up and offers you to disable the add-on or ignore it.

That window is a major distraction in instances
, so actually saying that we have to live with it because CT_Mod intentionally taints frames is not acceptable.

I've already dumped most of my CT_Mod addons, only the most essential ones remain until either the developer team finds ways to circumvent the issue where tainting triggers that "disable add-on" pop-up window (I wonder how they intend to do it when they told us not to report taint related messages) or I can get an add-on comparable to Raidassist.

If you think it is unlikely, believe me, it happened to Gatherer (Cartorapher Mining/Herbalism came as a replacement), it will happen to CT_raid.
  Reply With Quote
01-08-07, 08:42 AM   #9
Cide
Swedeheart
AddOn Author - Click to view addons
Join Date: Jan 2005
Posts: 96
Originally Posted by Cordelia
The problem with this approach is that, as far as I can see, ADDON_ACTION_BLOCKED and ADDON_FORBIDDEN messages are linked to that annoying UI window that pops up and offers you to disable the add-on or ignore it.

That window is a major distraction in instances
, so actually saying that we have to live with it because CT_Mod intentionally taints frames is not acceptable.

I've already dumped most of my CT_Mod addons, only the most essential ones remain until either the developer team finds ways to circumvent the issue where tainting triggers that "disable add-on" pop-up window (I wonder how they intend to do it when they told us not to report taint related messages) or I can get an add-on comparable to Raidassist.

If you think it is unlikely, believe me, it happened to Gatherer (Cartorapher Mining/Herbalism came as a replacement), it will happen to CT_raid.
Sigh, that's not what I said. At all. ADDON_ACTION_FORBIDDEN *does* pop up that annoying pop up, yes. ADDON_ACTION_BLOCKED, however, is entirely silent and transparent. Do you see even one ADDON_ACTION_FORBIDDEN in the original post, highlighting that such a pop up would show up? No, because there are none.

You don't have to threaten me and say that "your mods will get replaced" - that's fine, if there's a better mod then so be it. All I ask is that you don't misinterpret what I'm saying. I've never said anything like what you're suggesting - you're basing your argument on faulty facts.

Reporting taint is fine, but with CT_RaidAssist that's mostly useless information I'm afraid. The mod is quite old, and as such has not been coded to comply to the recent changes at all. Fixing up everything would take far too much time. Instead, CT_RaidAssist2 is on the horizon and is being coded to comply to all the changes, taint included.
__________________
CTMod Developer
  Reply With Quote

WoWInterface » AddOns, Compilations, Macros » AddOn Help/Support » Ctmod errors - *shown with bugsack.

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off