X-buZZ: Was there any pattern to things like your overall addon memory usage at the time of the crashes/errors?
What I'm pretty sure I'm seeing is that addons are creating garbage that WoW's LUA garbage collection is not able to recover. My overall memory usage climbs throughout the session, but the reported use of individual addons is not. Forced manual garbage collections do not reduce overall memory usage. Eventually, overall usage hits a magic number and I start getting the errors and then a crash.
As for the magic number, it seems to be relative to the amount of addon memory used at startup, rather than a fixed value, as I used to be getting it around 140MB with Cartographer+Prat+ArkInventory+others but am now seeing it at around 120MB with Mapster+Chatter+Baggins+others.
Using addons that are less aggressive with garbage creation seems to help to delay the issue, but it seems to be inevitable and the only current workaround is to reload my UI before i hit the magic number.
I would highly suggest keeping your addon memory usage under 100 MB irregardless, as I have not heard of anyone getting this error below that value.
ArkInventory has come under heavy fire for this crash because of its heavy use of memory, causing an extremely high rate of memory increase usage.
I've had the crash at between 80MB-90MB of reported AddOn memory in use before. Haven't seen it in a couple weeks, but I've admittedly played a little less, and been switching between alts more often, so probably not been on long enough in one sitting with a single character to trigger it.
Quote from PAusten »
[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>:
Would this indicate a crash at the Blizzard level in this case?
I've had the crash at between 80MB-90MB of reported AddOn memory in use before. Haven't seen it in a couple weeks, but I've admittedly played a little less, and been switching between alts more often, so probably not been on long enough in one sitting with a single character to trigger it.
What is your reported overall addon memory usage just after login/reloadui?
I have lately switch back to AI from baggins and I have not come across this problem since touch wood. What I have been doing though is prospecting ore with AI closed rather than leaving it open, this seems to be working for me at least. AI still pushes up memory but it's only a few megs over a about 2 minutes and settles down with a garbage dump soon after back down to around 3 megs total. One thing I did note that AI's addon memory does increase a lot quicker if you are stood with the mailbox open as well. not sure if that has anything to do with anything but thought I would mention it anyway.
I've now got my startup memory usage down to around 55MB as reported by PerformanceFu. I noticed that Option House reports my cumulative addon memory usage to be around 16MB less than that at startup, however, and the gap between the Option House reported number and the PerformanceFu reported number seems to grow over the course of the session, even after manual garbage collection. I suspect that the crash may be due to this gap growing too large and hitting some kind of hidden limit. If this is the case, then it may not matter how little memory my addons use at startup. This would also explain why people are seeing it happen at different total memory usage amounts.
What I'm pretty sure I'm seeing is that addons are creating garbage that WoW's LUA garbage collection is not able to recover. My overall memory usage climbs throughout the session, but the reported use of individual addons is not. Forced manual garbage collections do not reduce overall memory usage. Eventually, overall usage hits a magic number and I start getting the errors and then a crash.
I've had the same problem for months, for many many WoW patches. Mysterious increase of memory usage that's not connected to any of my addons according to PerformanceFu. It's usually not been a huge problem other than the game getting pretty choppy after around 80MB or so, but a quick Reload UI would fix it.
A few days ago, though, it started to actually throw multiple Bugsack errors and freeze my UI, forcing me to force-quit WoW because it'd just get stuck at the loading screen when trying to Reload UI in this state and throwing an Assertion Failed error. I'm not sure what suddenly caused this but it's gotta be something that happened around 2-3 days ago. Before then it never crashed due to high memory usage, even well above 100MB.
Actually, it's been almost nonexistant for me the past few weeks. I think I've seen it happen only like once or twice since my last report. Shuffled around some addons, but still using ArkInventory, Aloft and Skinner (one of these is usually what it seemed to attribute the error to, usually also including reference to Ace-OO [? or something like that]). Personally, I still think this may be a Blizzard issue, as I seem to recall seeing a couple of cases where it looked like the error was being thrown by something in the default Blizzard interface, and could have sworn I saw at least one report of this before where the individual was running zero addons, but don't quote me on that.
Sometime after the 2.4 WoW patch went live was the first I recall seeing this error, myself. With 2.4.1, I think my frequency for occurence was around the same as 2.4, but so far since 2.4.2 it seems to be behaving much better. Again, I'll also point to some addon shuffling on my part that may have helped in my case. For example, I have dumped Gatherer for GatherMate since I first received this error. Factor in some other addon replacements I've tried, various addon updates, some I've outright quit using altogether, driver and hardware updates, and I (unfortunately) can't offer much help in pinning down why mine seem to have all but disappeared. Sorry... :(
I read something on the Mac technical support forum (I have a Mac) about there being an error in Blizzard's code where some addons have calls which could cause a memory leak which would result in errors like this one, as well as Assertion Failed errors. Supposedly a fix is in testing for 2.4.3 but it's not in the patchnotes for some reason.
Interesting thread. When 2.4.3 is released I will test to see if I can get the usual memory usage that I get when I prospect ore with Ark open as well as the mailbox. I get around 500k/sec increase doing this till it stalls and eventually dies. If I don't have mailbox and ark open memory usage is around 3meg constant.
I've been experiencing this for a pretty long time now, for the longest time it'd occur after about 3-4hrs in a raid. I've never run into it outside of raids, leveling up alts for even longer periods of times.
Recently it started getting worse, occuring an hour or so after playing, removing ax_RaidStatus got it back to the old 3-4hr occurance.
I actually run into this problem frequently during 25 man raids (BT, sunwell, etc.) and it's really frustrating. I get around 30-35MB on load and between 35 and 45 during a raid but still get this problem. I've tried doing a /rl or /reloadui and that just crashes wow and gives me a wowerror. The only way to end it is to ctrl alt delete and restart wow. I'm getting a new computer this week so I may or may not have this problem after then. But just in case/for preventive measure, here's a screenshot of my addon list. Any help would be greatly appreciated.
i wonder if the old 'scriptMemory' variable inside the config.wtf has so,mething to do with this...
Does any one knows what the exact purpose of this setting was before it has been removed from the ingame options?
i wonder if the old 'scriptMemory' variable inside the config.wtf has so,mething to do with this...
Does any one knows what the exact purpose of this setting was before it has been removed from the ingame options?
Kind regards
X-buZZ
A blue post I found on google from a few months ago states that the scriptMemory cvar has been ignored by WoW for quite some time. I know that quite a few patches ago they changed it from having a hard, user-specified limit to supposedly having no addon memory usage cap (made possible by garbage collection and whatnot).
I still wonder if it isn't that there is a fixed amount of memory allocated to some kind of metadata in WoW's LUA engine, possibly relating to garbage collection or tables, and that this memory limit is being overrun by addons that are too aggressive with memory allocation and/or garbage creation and/or creation/deletion of tables.
I've been experiencing this for quite a while now. Usually it's not a big deal -- it often happens right at the end of a raid for some weird reason. It doesn't happen much (if ever) when I'm soloing on my shadow priest main.
However, it happens quite often on my hunter. I have yet to be able to make out any pattern as to when it happens. I've pretty much stopped leveling my hunter until this problem goes away.
Here's hoping that the 2.4.3 patch will fix it.
/crossfingers
All I can say, though, is that I'm fairly sure it can't be the addons' fault -- addons shouldn't have direct memory access, only through the WoW LUA interface. The interface must be somehow failing to do memory allocation correctly.
And I should also add that on rare occasions, this error will happen and a /console reloadui will actually WORK! Most of the time, the client crashes, but sometimes it'll recover.
Are there any error logs that will provide some clues if I can get the UI to reload without the client crashing?
DATA POINT
i'm suspecting a tooltip mod...
for me it happens most of the time when im hovering over a piece of equipment in the Char screen or loot tables.
i have to /camp to unlock unfortunately i can open bugsack due to the lock...
im change around some loot/tooltip mods, to see if i can't narrow it down or at least rule out a couple.
Doc
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
What I'm pretty sure I'm seeing is that addons are creating garbage that WoW's LUA garbage collection is not able to recover. My overall memory usage climbs throughout the session, but the reported use of individual addons is not. Forced manual garbage collections do not reduce overall memory usage. Eventually, overall usage hits a magic number and I start getting the errors and then a crash.
As for the magic number, it seems to be relative to the amount of addon memory used at startup, rather than a fixed value, as I used to be getting it around 140MB with Cartographer+Prat+ArkInventory+others but am now seeing it at around 120MB with Mapster+Chatter+Baggins+others.
Using addons that are less aggressive with garbage creation seems to help to delay the issue, but it seems to be inevitable and the only current workaround is to reload my UI before i hit the magic number.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumArkInventory has come under heavy fire for this crash because of its heavy use of memory, causing an extremely high rate of memory increase usage.
I've had the crash at between 80MB-90MB of reported AddOn memory in use before. Haven't seen it in a couple weeks, but I've admittedly played a little less, and been switching between alts more often, so probably not been on long enough in one sitting with a single character to trigger it.
Would this indicate a crash at the Blizzard level in this case?
What is your reported overall addon memory usage just after login/reloadui?
Will most likely be different now, as I've done some addon shuffling and such since then. Can't recall what it was at the time right after login.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've had the same problem for months, for many many WoW patches. Mysterious increase of memory usage that's not connected to any of my addons according to PerformanceFu. It's usually not been a huge problem other than the game getting pretty choppy after around 80MB or so, but a quick Reload UI would fix it.
A few days ago, though, it started to actually throw multiple Bugsack errors and freeze my UI, forcing me to force-quit WoW because it'd just get stuck at the loading screen when trying to Reload UI in this state and throwing an Assertion Failed error. I'm not sure what suddenly caused this but it's gotta be something that happened around 2-3 days ago. Before then it never crashed due to high memory usage, even well above 100MB.
More infos about my particular errors: http://www.wowace.com/forums/index.php?topic=14020
Any updates regarding this problem?
Sometime after the 2.4 WoW patch went live was the first I recall seeing this error, myself. With 2.4.1, I think my frequency for occurence was around the same as 2.4, but so far since 2.4.2 it seems to be behaving much better. Again, I'll also point to some addon shuffling on my part that may have helped in my case. For example, I have dumped Gatherer for GatherMate since I first received this error. Factor in some other addon replacements I've tried, various addon updates, some I've outright quit using altogether, driver and hardware updates, and I (unfortunately) can't offer much help in pinning down why mine seem to have all but disappeared. Sorry... :(
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://forums.worldofwarcraft.com/thread.html?topicId=6441116352&sid=1&pageNo=1
I've been experiencing this for a pretty long time now, for the longest time it'd occur after about 3-4hrs in a raid. I've never run into it outside of raids, leveling up alts for even longer periods of times.
Recently it started getting worse, occuring an hour or so after playing, removing ax_RaidStatus got it back to the old 3-4hr occurance.
http://img296.imageshack.us/img296/6395/addonssds7.jpg
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi wonder if the old 'scriptMemory' variable inside the config.wtf has so,mething to do with this...
Does any one knows what the exact purpose of this setting was before it has been removed from the ingame options?
Kind regards
X-buZZ
A blue post I found on google from a few months ago states that the scriptMemory cvar has been ignored by WoW for quite some time. I know that quite a few patches ago they changed it from having a hard, user-specified limit to supposedly having no addon memory usage cap (made possible by garbage collection and whatnot).
I still wonder if it isn't that there is a fixed amount of memory allocated to some kind of metadata in WoW's LUA engine, possibly relating to garbage collection or tables, and that this memory limit is being overrun by addons that are too aggressive with memory allocation and/or garbage creation and/or creation/deletion of tables.
http://www.wowace.com/forums/index.php?topic=2278.msg226777#msg226777
http://www.wowace.com/forums/index.php?topic=12443.msg226431#msg226431
I've been experiencing this for quite a while now. Usually it's not a big deal -- it often happens right at the end of a raid for some weird reason. It doesn't happen much (if ever) when I'm soloing on my shadow priest main.
However, it happens quite often on my hunter. I have yet to be able to make out any pattern as to when it happens. I've pretty much stopped leveling my hunter until this problem goes away.
Here's hoping that the 2.4.3 patch will fix it.
/crossfingers
All I can say, though, is that I'm fairly sure it can't be the addons' fault -- addons shouldn't have direct memory access, only through the WoW LUA interface. The interface must be somehow failing to do memory allocation correctly.
And I should also add that on rare occasions, this error will happen and a /console reloadui will actually WORK! Most of the time, the client crashes, but sometimes it'll recover.
Are there any error logs that will provide some clues if I can get the UI to reload without the client crashing?
i'm suspecting a tooltip mod...
for me it happens most of the time when im hovering over a piece of equipment in the Char screen or loot tables.
i have to /camp to unlock unfortunately i can open bugsack due to the lock...
im change around some loot/tooltip mods, to see if i can't narrow it down or at least rule out a couple.
Doc