It is a clear indicator that the code that calls lua at this point is buggy. As you can see, these errors occur in SetScript() or SetAttribute(), further proof that the bug is not at all in lua code, but in the C wrapping code.
I have never encountered this bug myself. It's quite possible that Blizzard never did either, and thus can't correct it.
Uhm, yeah. Except I sent Zootfizzle a crash dump from such a crash. See my post above. Maybe you could report this on the official forums. Maybe Slouken will hear more of it than Zootfizzle will.
Cowtip seemed to be it for me as well. I recently replaced it with tiptac and haven't had this error since. We're doing a near-full clear of BT later this week so hopefully that'll be a long enough test for it.
After rewriting my whole tooltip i started crashing again around ~100mb, disabled cowtip, no problem, so i think there's something wrong with dogtags. the default settings cowtip worked for me, no crashes.
Uhm, yeah. Except I sent Zootfizzle a crash dump from such a crash. See my post above. Maybe you could report this on the official forums. Maybe Slouken will hear more of it than Zootfizzle will.
I don't have access to the US forums. BTW, unless someone experiences this in the latest beta, there's no real point in doing so. Basically, the current client is broken, and dogtag or whatever just shows that its buggy. You may hope that the beta client does not have this bug anymore. Unless you experience it in the beta client, I'm not sure it will be investigated.
I don't have access to the US forums. BTW, unless someone experiences this in the latest beta, there's no real point in doing so. Basically, the current client is broken, and dogtag or whatever just shows that its buggy. You may hope that the beta client does not have this bug anymore. Unless you experience it in the beta client, I'm not sure it will be investigated.
Which is why I was asking in reply #136 if anyone has seen this in beta.
Its not calling itself in a endless loop if that is what you are asking. The inner call to module:OnModuleEnable doesnt call into the outer closure. (I think)
obviously the following corrected code works:
local orgOME = module.OnModuleEnable
function module:OnModuleEnable(...)
orgOME(self, ...)
if WIM then
WIM.RegisterWidgetTrigger("chat_display", "whisper,chat,w2w,demo", "OnHyperlinkClick", function(...) self:ChatFrame_OnHyperlinkShow(...) end);
end
end
I had this error 4 times in Black Temple the other night.
I made a post about it in the CowTip forums over here. I attached 4 error messages.
Is it the consensus that this is a problem with the latest client? Does it look like Blizzard will be fixing this or is it something add-on developers will have to code around?
All of my errors in the last few weeks seem to be related to AceEvent-2.0. Is this problem confined to Ace2, and if so, is it worth porting the most popular of these add-ons to Ace3 or Rock?
Still haven't seen this in a while, but yes, AceEvent-2.0 was involved in most (all..? ...can't recall now) of the errors I witnessed in the past. The addon actually throwing the error would change, but AceEvent-2.0 seemed to usually be in the stack as the only common denominator I remember seeing.
I had this error 4 times in Black Temple the other night.
I made a post about it in the CowTip forums over here. I attached 4 error messages.
Is it the consensus that this is a problem with the latest client? Does it look like Blizzard will be fixing this or is it something add-on developers will have to code around?
All of my errors in the last few weeks seem to be related to AceEvent-2.0. Is this problem confined to Ace2, and if so, is it worth porting the most popular of these add-ons to Ace3 or Rock?
Had the same kind of errors in BT when I ran it a few nights ago. I have cowtip and pitbull installed.
[2008/11/04 02:09:26-211-x40]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:421: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:302: in function <Interface\AddOns\CowTip\Appearance\Appearance.lua:297>
<in C code>: in function `SetUnitBuff'
Outfitter-4.3b10\Outfitter.lua:4254: in function `GetBuffTooltipText'
Outfitter-4.3b10\Outfitter.lua:4237: in function `GetPlayerAuraStates'
Outfitter-4.3b10\Outfitter.lua:4294: in function `UpdateAuraStates'
Outfitter-4.3b10\Outfitter.lua:4842: in function <Interface\AddOns\Outfitter\Outfitter.lua:4842>
<in C code>: in function `pcall'
Outfitter-4.3b10\MCEventLib.lua:203: in function `DispatchEvent'
Outfitter-4.3b10\MCEventLib.lua:65: in function <Interface\AddOns\Outfitter\MCEventLib.lua:65>
---
[2008/11/04 02:09:26-211-x1]: memory allocation error: block too big:
<in C code>: in function `SetScript'
Quartz_Player-1.0\Player.lua:142: in function <Interface\AddOns\Quartz_Player\Player.lua:141>
<in C code>: in function `Show'
Quartz_Player-1.0\Player.lua:313: in function <Interface\AddOns\Quartz_Player\Player.lua:295>
(tail call): ?:
(tail call): ?:
Quartz_Latency-1.0\Latency.lua:86: in function <Interface\AddOns\Quartz_Latency\Latency.lua:85>
(tail call): ?:
<in C code>: ?
AceEvent-2.0-91091 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-91091 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
[2008/11/04 02:09:26-211-x2]: AceEvent-2.0-91091 (Ace2):299: memory allocation error: block too big
---
[2008/11/04 02:09:27-211-x2]: memory allocation error: block too big:
<in C code>: in function `SetScript'
Omen-3.0.1\Omen.lua:931: in function `AnimateTo'
Omen-3.0.1\Omen.lua:1458: in function `UpdateBars'
Omen-3.0.1\Omen.lua:1082: in function `?'
CallbackHandler-1.0-3 (Ace3):146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[2]":4: in function <[string "safecall Dispatcher[2]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[2]":13: in function `?'
CallbackHandler-1.0-3 (Ace3):91: in function `Fire'
AceEvent-3.0-3 (Ace3):70: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:69>
---
[2008/11/04 02:09:28-211-x15]: AceEvent-2.0-91091 (Ace2):369: memory allocation error: block too big
The last 2-3 posts might give you some practical things to try with CowTip.
For those with a technical inclination the rest of the thread will provide an "answer" as to what's happening and who's to "blame".
If you can't follow the details just stick with the practical tips found at the end of the thread.
Every time this comes up I see a few people that pick random words (ace2, cowtip, arkinventory ...)
and recite a mantra that would protect their favorite addon from getting blame.
Removing CowTip worked for me. I've had a mysterious memory increase without 'owner' of all this used memory for months and since I got rid of it my memory during raids in particular hasn't gone above 40mb since (used to rise above 80mb+ where it'd cause my client to crash due to memory allocation etc).
Losing CowTip was rough because I love the dogtags and their customizability but I found a good and similar replacement with TipTac, without memory issues. ;)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I don't have access to the US forums. BTW, unless someone experiences this in the latest beta, there's no real point in doing so. Basically, the current client is broken, and dogtag or whatever just shows that its buggy. You may hope that the beta client does not have this bug anymore. Unless you experience it in the beta client, I'm not sure it will be investigated.
Which is why I was asking in reply #136 if anyone has seen this in beta.
Sadly it was during some intermediate version before I actually finished updating the addon and I don't have that "broken" code.
But it IS possible to get the error from addons on wow 3.x.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiummodule.OnModuleEnable = function(...) module:OnModuleEnable(...) WIM.RegisterWidgetTrigger("chat_display", "whisper,chat,w2w,demo", "OnHyperlinkClick", function(...) module:ChatFrame_OnHyperlinkShow(...) end); end-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIts not calling itself in a endless loop if that is what you are asking. The inner call to module:OnModuleEnable doesnt call into the outer closure. (I think)
obviously the following corrected code works:
local orgOME = module.OnModuleEnable function module:OnModuleEnable(...) orgOME(self, ...) if WIM then WIM.RegisterWidgetTrigger("chat_display", "whisper,chat,w2w,demo", "OnHyperlinkClick", function(...) self:ChatFrame_OnHyperlinkShow(...) end); end end-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo it means nothing of the sort.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI made a post about it in the CowTip forums over here. I attached 4 error messages.
Is it the consensus that this is a problem with the latest client? Does it look like Blizzard will be fixing this or is it something add-on developers will have to code around?
All of my errors in the last few weeks seem to be related to AceEvent-2.0. Is this problem confined to Ace2, and if so, is it worth porting the most popular of these add-ons to Ace3 or Rock?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHad the same kind of errors in BT when I ran it a few nights ago. I have cowtip and pitbull installed.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://forums.wowace.com/showthread.php?t=14666
The last 2-3 posts might give you some practical things to try with CowTip.
For those with a technical inclination the rest of the thread will provide an "answer" as to what's happening and who's to "blame".
If you can't follow the details just stick with the practical tips found at the end of the thread.
Every time this comes up I see a few people that pick random words (ace2, cowtip, arkinventory ...)
and recite a mantra that would protect their favorite addon from getting blame.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLosing CowTip was rough because I love the dogtags and their customizability but I found a good and similar replacement with TipTac, without memory issues. ;)