I've only had this errors for a couple of days now, and I had a hard tome to retrieve the error message, since after the bug I couldn't click or use BugGrabber at all. Anyway, my error is:
[2008/05/22 19:01:19-2830-x3]: memory allocation error: block too big:
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureStateDriver.lua:98: in function Interface\FrameXML\SecureStateDriver.lua:79>:
and I can't think of a reason for it to happen, since I had to leave the computer for a couple minutes and when I came back it had the BugGrabber window up (I told it to pop up after an error)
Hope it helps.
- Registered User
Member for 12 years, 10 months, and 15 days
Last active Fri, Oct, 4 2013 14:30:03
- 0 Followers
- 11 Total Posts
- 0 Thanks
May 22, 2008_ForgeUser246964 posted a message on ERROR: Memory allocation error: Block too big. Count: InfinitePosted in: AddOn HELP!
Mar 25, 2008After updating to 65853, omen just doesn't show up at all in my screen, same with it's fubar button and it's entry on the rock config window.Posted in: Raid AddOns
Bugsack does't show any errors.
Ace3, Threat-2.0 and libsink-2.0 are installed.
Forgot to say: playing on a US Realm
Nov 27, 2007As I was talking to my sister earlier today, she plays a hunter, about this wonderful addon, she showed some interest about how would this addon deal with the traps. She wanted to know if this addon could not only show the cooldown for the trap, but also show for how long the trap is going to be up (activated so a mob could get frozen/set on fire/etc).Posted in: General AddOns
I don't know if this "feature" would be useful for other classes, maybe it will for shamans, but I thought I'd request it anyway.
So, for short, when using a freeze trap, two bars would be created, one for the trap cooldown, and the other one showing for how long the trap would be active on the floor.
Thanks in advance.
Sep 25, 2007@OrionShockPosted in: General AddOns
I know you probably have ppl posting without reading stuff, but i'm afraid i don't fit in that category. That error I posted made itself present after Syzgyn's quick fix got commited.
Gonna try that right now, thanks.
After trying Astaldo's quick fix, which solves the IsAutoLootKeyDown() error, the frame pops up, but i can't single loot the corpse, but i can still auto loot everything on the corpse by "shift+clicking". When i try to single loot the corpse, i get the following error:
[2007/09/25 20:32:58-1400-x6]: XLoot-0.9.49761\XLoot.lua:341: attempt to call field 'LootButton_OnModifiedClick' (a nil value) (tail call): ?: <string>:"*:OnClick":4: in function <[string "*:OnClick"]:1>
Sep 25, 2007Hello,Posted in: General AddOns
I think you guys already know this, but here's the error message I keep getting every 5 seconds or so...
[2007/09/25 19:42:18-1395-x6]: XLoot-0.9.49761\XLoot.lua:137: attempt to call global 'IsAutoLootKeyDown' (a nil value) XLoot-0.9.49761\XLoot.lua:258: in function <Interface\AddOns\XLoot\XLoot.lua:257> (tail call): ?:
I got this error after updating it to "R49761" a few moments before logging in tonight.
Jul 21, 2007More about this issue:Posted in: Unit Frames
Disabling Stubby did indeed solve the problem for a while, but now the problem is back, although it doesn't happen that often, it seems that it's bound to break when enter/leave an instance.
I've only seen it break once when hearthing.
Jul 20, 2007Ok, i found out what was going on...Posted in: Unit Frames
I still had an add on called "Stubby", from when i wasn't using only ACE2 add-ons, it seems that it interferes with some functions from pitbull.
you might want to check disabling Stubby if you have it...
Hope this helps.
Jul 19, 2007Hello everyone,Posted in: Unit Frames
Just like the above user, i searched everywhere for an updated post about Pitbull and the Target frame not being updated properly issue.
I noticed that, when you log on, everything works fine, but after some time playing, the Target Frame just refuses to update, sometimes only the portrait, sometimes the Health Bar + Portrait + Power bar.
Also, I noticed that it usually happens when you enter/leave and instance.
I'm pretty new to ace add-ons, but I'm already using WAU to keep everything in place and updated, but this Target Frame issue is almost making me go back to X-Perl or try something other than Pitbull.
Could you please update us about this problem?
Thanks in advance,
- To post a comment, please login or register a new account.