I get the (memory allocation error:block too big, Count: infinite) error every day or so, completely unpredictable, but whenever it happens i have to crash my wow to fix it. every ace mod i have bugs out and no longer works (along with some non ace mods), and when i try to log out or exit, i get an error window - but its a tiny error box with no number, just a single word. it is starting to get annoying... at first i thought it might be a bug within ace, but i continued updating and it stayed, so now im wondering if its just me or if anyone else is encountering something like this, or has heard of it?
EDIT: just got it again, and its not just mods, i cant hit escape and use the blizzard menus either.
Addon\AtlasLoot\Libs\AceEvent-2.0\AceEvent-2.0.lua:369:memory allocation error:block too big
Except its not an Atlas Loot issue. If I disable atlas Loot, the error just moves down to the next Ace2 mod Im running, rinse and repeat. After this first error comes up, ever Ace2 mod breaks. I have to crash out as well to fix it.
Try the reverse process. Start with no addons. Then enable your addons one by one until the problem starts to happen.
The problem is of course not with AtlasLoot. In the error message above
"Addon\AtlasLoot\Libs\AceEvent-2.0\AceEvent-2.0.lua:369:memory allocation error:block too big"
the error is saying that the AveEvent-2.0 shared library is causing issues, and any of your Ace addons using this library can be the culprit. It is just that the copy of AceEvent-2.0 loaded by AtlasLoot happens to be used first.
[2008/04/14 11:57:44-512-x6]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
Skinner-2.4\Skinner.lua:394: in function `keepFontStrings'
Skinner-2.4\SkinMe\ArkInventory.lua:94: in function <Interface\AddOns\Skinner\SkinMe\ArkInventory.lua:91>
(tail call): ?:
<in C code>: in function `Frame_Main_Draw'
ArkInventory-2.27\ArkInventory.lua:4185: in function `Frame_Main_DrawLocation'
ArkInventory-2.27\ArkInventory.lua:4176: in function `Frame_Main_Generate'
ArkInventory-2.27\ArkInventory.lua:1816: in function `?'
AceEvent-2.0-66043:695: in function <...s\AckisRecipeList\libs\AceEvent-2.0\AceEvent-2.0.lua:682>
<in C code>: ?
AceEvent-2.0-66043:368: in function <...s\AckisRecipeList\libs\AceEvent-2.0\AceEvent-2.0.lua:345>
Here's a copy of the error message I get on my bank/auction alt. I tend to get this error to pop at the mailbox which leads me to believe Postal, ArkInventory or FuBarMailFu might be involved
I would suggest investigating ArkInventory as the most likely suspect. It's really bad about generating megabytes worth of tables and then orphaning them as garbage, every time something in your bags changes.
I've seen this error as well, and I use the 3 addons that yegg listed, although it seems to happen more often in raids than in solo play.
I doubt it's AI as I've gotten it a few times myself after playing for a few (4-6) hours and do not have AI.
I have noticed the error message moves around a bit is never the same (sometimes it's even a blizz function/file).
This is what I've seen: My normal memory usage is 50-70mb. After a few 3-4 hours I look down and it's up to say 80-90 no biggie there (though could probably scale down my addons). When the error occurs I look down and it's at 140+mb . . . just this spike and then nothing can happen, no frames can be created, though already up frames usually work ok. I haven't had the problem lately as I've removed a few higher memory addons, but I still see the spike after 4-5 hours of questing (and now just do a /rl to make sure it doesn't hit me)
Not sure if any of that is useful. The odd thing is that once it hits, showing/hiding or creating ANY frame causes another error and fails. Ie can't bring up any menus, even the edit bar will not work unless it was up when the errors started (and then it won't hide).
For now I'm just avoiding the error by watching my memory once I have more time I'll just start paring down my addons.
Yeah 140-150MB of usage seems to be when it happens, and it's usually when raiding because that's when I have the most addons active. It happened again last night, and I've switched from AI to Baggins to see if it helps.
At login my usage is ~85MB (increases 10-20MB when joining a raid), and it seems to climb slowly but steadily. It will cause a crash almost without fail if I don't reload my UI by the time I'm 3 hours or so into a raid and my memory usage has climbed above 140MB. I force garbage collections constantly to keep memory usage down because I'm now paranoid about the crashes, and usually I try to find an opportunity to reload my UI before usage hits 140MB.
AI may not be the problem, but the fact that it creates 5MB of additional garbage every time something changes in your bags and/or whenever you open your bags greatly exacerbates the issue. For those testing, it may be a good way to try to replicate the issue though.
Can't specifically be CowTip, as I don't run that here, and still have seen this happen twice so far (only after extended play sessions).
As for the possible mailbox interference, as far as I can recall, I've only got AI and BeanCounter (from AucAdvanced package) that seems to do anything with the mailbox. However, since people are reporting it in raid (well away from a mailbox), I'd tend to agree that the mailbox probably has nothing to do with it.
I'm pretty sure that both times I've seen it so far, I was solo, so even group size may not have any bearing on it either. But, I had been in party earlier in the session, so I guess this can't be ruled out altogether.
Sorry, I'm probably not being much help, but I figured some small bit of info was better than none. :P
MegaManJuno: Did you notice what your total addon memory usage was at the time of the crash(es)?
I didn't think to check that at the time, but as far as actual free physical memory goes, I know I had at least a half-gig free. My initial thought was that since I had some stuff running in the background during the first crash that I had possibly maxed out my physical memory usage, but that wasn't the case.
If I see it happen again, I'll try to remember to take note of the AddOn memory usage reported and post back here.
There is a possibility more than one addon could be causing the same issue. Disable AI and see if it goes away.
I used Baggins+Possessions+WhoHas last night, which combined have a lower memory usage, and none of the problems with 5MB tables thrown onto the garbage heap every few seconds. However, I still eventually got the out of memory error issue at a bit under 140MB of total addon memory usage reported by performancefu, which was followed by the strange addon behavior and ultimately the same WoW crash when I tried to log out of the game.
It seems to be a different library or addon generating the out of memory error every time, so I think that's a red herring. Something else (addon, library, or the game itself?) is gobbling up some limited memory block in the scripting engine and causing addons to misbehave, followed by a WoW client crash.
I find it really annoying and it ALWAYS occurs at a mailbox for me. I do a lot of mailbox activity, there's 50 items/letters, I open all, go back, there's 50 more, and go back, there's 50 more and it crashes. Same error message.
I find that any frames open at the time are 'locked' open. (For instance, my mailbox stays open even when I walk away from it.) The game gets incredibly laggy, as if it's processing an infinite loop. (I really think infinite loop is causing this.) No frames become visible afterward, but blizzard frames still 'work'. (I can talk to a vendor and sell stuff, though I don't see the window.)
/console reloadui causes the game to 'disconnect' after attempting to reload, sometimes a crash, sometimes just so laggy it's a disconnect. So it apparently is still on an infinite loop even after a reload.