ERROR: Memory allocation error: Block too big. Count: Infinite

[sag_ich_nicht]

Originally Posted by Jerry

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.

[Awwe]

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.

[quzzap]

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.

[jerry]

Originally Posted by sag_ich_nicht

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.

[HunterZ]

Originally Posted by Jerry

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.

[astaldo2]

I have seen this in beta in the sense that I made it happen myself while updating Talent Planner by TheGabbert.

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.

[sylvanaar]

I just created the error on beta. this code did it.

 
module.OnModuleEnable = function(...) 
   module:OnModuleEnable(...)
   WIM.RegisterWidgetTrigger("chat_display", "whisper,chat,w2w,demo", "OnHyperlinkClick", function(...) module:ChatFrame_OnHyperlinkShow(...) end);
end

[Arrowmaster]

How did that not lockup your client?

[sylvanaar]

Originally Posted by Arrowmaster

How did that not lockup your client?

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

[X-buZZ]

Does that mean that WIM is causing the memory issue?