Tried without ErrorMonster enabled and still crashed yesterday. It seems that since I've been paying closer attention to the error messages lately, that no matter which one is reported as the source of the error (ArkInventory, Skinner, & AtlasLoot are ones I know I've seen so far), I'm always seeing AceEvent-2.0 included in the error message. One thing I hadn't thought to ask before: is everyone posting here with the issues running embedded (I am)? I'm starting to wonder if this may be an issue with one or more of the addons I'm running having an older AceEvents-2.0 embed than another is looking for, and differences between the two are causing it...?
I run with embedded libs as well, update using WUU on Mac OS X 10.5.2. A lot of times when this occurs I can't even look at bugsac to get the error message. doing a /reloadui causes wow to crash and pop up the crash reporter. Given that we're seeing it with a variety of circumstances and addons, perhaps it is a lib issue rather than a specific addon? I dunno, I'm no coder, I'm just trying to see a common pattern here.
I'm running standalone... and it's not only AceEvent-2.0 it's TabletLib-2.0 for me too. But I'm running also Arkinventory and errors ocurs for me only at the mailbox/disenchanting/prospecting...
I get the same exact errors as you guys are getting. It happens on a disenchanting alt 3 or 4 times per session. All I do with this alt is buy items on the AH, anywhere from 70 on a slow day up to over 200 items on a Monday. The error will occur at the mailbox as I gather the items...I DE them as I gather the items and the error always occurs when DE'ing the items, sometimes 3 or more times depending on how large my inbox is. I use ArcInventory and Auctioneer Advanced. I will also get the errors when posting my enchanting mats to the AH. If I have a full bag of enchanting mats it always procs, but I can continue listing the items. then I just /quit to leave the game. I haven't noticed the memory usage at the time of the crashes but I will the next time it happens.
EdSurly: Both /quit & /logout crash the game for me altogether after this error occurs, as well as attempting to reload ui... are you actually able to exit this way without the client crash?
So much data collection has been getting lost on my end due to this error, since nothing gets written back due to the client crash on exit. MobInfo, Auctioneer scan data, any changes I may make to addon settings, etc.... it sucks. So, I've taken to doing a reload of the ui every so often now to try and compensate for it. :(
For data collection purposes, I find that /console reloadui keeps the data. It takes forever, but the game reloads, and then crashes, and that reload allows collected data to be saved.
I'm running with non-embedded libraries as much as possible. I find that reloading my UI before it gets bad will usually prevent things from going bad, but if I attempt to reload my UI after I start getting memory errors, I'll always get a crash.
Also, I've only had one crash since disabling ArkInventory, but I think it's just because AI was aggressive about frequently allocating memory and then throwing it on the garbage heap.
I don't run Auctioneer on my raiding toon (the only toon that's crashed I think) but I do run some pieces like Informant, Stubby and maybe BeanCounter (and maybe EnhTooltip?). I also run SharedMedia and ErrorMonster but none of the others from Thortok2000's list.
Something else I've noticed since 2.4 is that even when I don't get those errors, my game will almost always freeze at the login screen when I attempt to exit after a long play session (a couple hours or more). I've left it running for hours to see if it would exit, and it doesn't - I have to kill the process.
I find that reloading my UI before it gets bad will usually prevent things from going bad, but if I attempt to reload my UI after I start getting memory errors, I'll always get a crash.
Same.
Quote from HunterZ »
Also, I've only had one crash since disabling ArkInventory, but I think it's just because AI was aggressive about frequently allocating memory and then throwing it on the garbage heap.
Yeah, I think while it may contribute to the issue, I'm not sure it's the cause. I'm pretty sure I recall seeing somewhere that someone mentioned they weren't running AI at all and still got the same crashes.
Quote from HunterZ »
Something else I've noticed since 2.4 is that even when I don't get those errors, my game will almost always freeze at the login screen when I attempt to exit after a long play session (a couple hours or more). I've left it running for hours to see if it would exit, and it doesn't - I have to kill the process.
I'm pretty sure from what little I've read over on the WoW support forums, that this is a Blizzard bug that was supposed to have been fixed in 2.4.1. Apparently, some people are still having issues with it though (2.4.1 seems to have corrected it for me so far though).
EdSurly: Both /quit & /logout crash the game for me altogether after this error occurs, as well as attempting to reload ui... are you actually able to exit this way without the client crash?
Sorry for the mix-up, no the game does indeed crash. I get the pop-ups asking to send the info to BLizzard and the windows error message.
Ok, got the error two more times while gathering disenchantables off the mailbox and while listing my enchanting mats to the AH. The first time, while getting my stuff (disenchantables) off the mail box I watched as my used memory climbed from an initial amount of 70 mb up to 170mb with ArkInventory taking the lions share of the increasing rate (in the range of +5-8mb) my usage dropped from the 170mb level down to 140mb or so with Ark's increasing rate also dropping (Note, I was not decreasing MY rate of gathering items from the mailbox) as my overall memory usage increased back up it hit 158mb or so I heard the tell-tale *ding when the first error hit. I tried the /reload ui tip from someone else posting here and the game DID NOT CRASH! My ui reloaded and my memory usage went back to the initial 70mb. I got the rest of my mats, disenchanted then made my way to the AH.
At the aution house while posting my mats, I had a rather large amount of Greater Nether Essence (77 units) and I post these individually (dont hate me for spamming the AH :)) with an eye on my memory usage rising past 140mb I see that ArkInventory's increading usage passing 8mb, then 11mb, then 17mb finally topping out at a whopping 24mb increasing usage before dropping back to 5mb and my overall memory usage falling from the 160mb level back to 145mb. As I continued to load items on the AH Ark started climbing again hitting only about 8mb increasing rate and my overall memory usage getting to 155mb and I get the error again. I continued to post the rest of my mats and upon completing that task my memory usage was up around 198mb. I tried the /reload ui tip again but this time the game crashed...but here's where it got wierd. I did not get the windows error message nor did I get the Blizzard window asking me to send the error to them. First time that hasn't happend with this error.
I hope I didn't waste my time in posting this and I hope your time wasn't wasted in reading it.
While nobody really knows what is causing the game to crash yet, what is clear is that ArkInventory needs a rewrite to stop that crazy rate of increasing memory usage.
It is somewhat clear that allocating memory in WoW is what is causing the crashes and addons that have a high rate of memory usage increase tends to be the ones that causes the crash, and that AI isn't the only such addon, but just one of the many possible ones. AI seems to be a common culprit only because it has the highest rate of memory use compared to every other addon.
While nobody really knows what is causing the game to crash yet, what is clear is that ArkInventory needs a rewrite to stop that crazy rate of increasing memory usage.
It is somewhat clear that allocating memory in WoW is what is causing the crashes and addons that have a high rate of memory usage increase tends to be the ones that causes the crash, and that AI isn't the only such addon, but just one of the many possible ones. AI seems to be a common culprit only because it has the highest rate of memory use compared to every other addon.
Or simply (for those of us running embedded) the fact that AI is one of the first addons loaded alphabetically, so embedded libraries get attached to it...? So far, it's looking to me like a library issue (AceEvent-2.0 perhaps?) or a Blizzard bug.
Or simply (for those of us running embedded) the fact that AI is one of the first addons loaded alphabetically, so embedded libraries get attached to it...? So far, it's looking to me like a library issue (AceEvent-2.0 perhaps?) or a Blizzard bug.
Or simply (for those of us running embedded) the fact that AI is one of the first addons loaded alphabetically, so embedded libraries get attached to it...? So far, it's looking to me like a library issue (AceEvent-2.0 perhaps?) or a Blizzard bug.
If what you said is really true, then disabling ArkInventory would have just pushed the problem to the next addon that embeds Ace2. However reports are contrary to this, that disabling AI more often than not tends to solve the problem by removing the enormous memory usage growth.
If what you said is really true, then disabling ArkInventory would have just pushed the problem to the next addon that embeds Ace2. However reports are contrary to this, that disabling AI more often than not tends to solve the problem by removing the enormous memory usage growth.
Indeed. I do not run with libraries embedded, and still chronically suffered from this issue while running ArkInventory. AI is EXTREMELY aggressive in terms of frequently allocating and almost immediately trashing large chunks of memory (5+MB) whenever something changes in your bags in order to create sorting tables to update the display. For some reason, Baggins doesn't seem to suffer from this issue.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So much data collection has been getting lost on my end due to this error, since nothing gets written back due to the client crash on exit. MobInfo, Auctioneer scan data, any changes I may make to addon settings, etc.... it sucks. So, I've taken to doing a reload of the ui every so often now to try and compensate for it. :(
Also, I've only had one crash since disabling ArkInventory, but I think it's just because AI was aggressive about frequently allocating memory and then throwing it on the garbage heap.
I don't run Auctioneer on my raiding toon (the only toon that's crashed I think) but I do run some pieces like Informant, Stubby and maybe BeanCounter (and maybe EnhTooltip?). I also run SharedMedia and ErrorMonster but none of the others from Thortok2000's list.
Something else I've noticed since 2.4 is that even when I don't get those errors, my game will almost always freeze at the login screen when I attempt to exit after a long play session (a couple hours or more). I've left it running for hours to see if it would exit, and it doesn't - I have to kill the process.
Same.
Yeah, I think while it may contribute to the issue, I'm not sure it's the cause. I'm pretty sure I recall seeing somewhere that someone mentioned they weren't running AI at all and still got the same crashes.
I'm pretty sure from what little I've read over on the WoW support forums, that this is a Blizzard bug that was supposed to have been fixed in 2.4.1. Apparently, some people are still having issues with it though (2.4.1 seems to have corrected it for me so far though).
Sorry for the mix-up, no the game does indeed crash. I get the pop-ups asking to send the info to BLizzard and the windows error message.
At the aution house while posting my mats, I had a rather large amount of Greater Nether Essence (77 units) and I post these individually (dont hate me for spamming the AH :)) with an eye on my memory usage rising past 140mb I see that ArkInventory's increading usage passing 8mb, then 11mb, then 17mb finally topping out at a whopping 24mb increasing usage before dropping back to 5mb and my overall memory usage falling from the 160mb level back to 145mb. As I continued to load items on the AH Ark started climbing again hitting only about 8mb increasing rate and my overall memory usage getting to 155mb and I get the error again. I continued to post the rest of my mats and upon completing that task my memory usage was up around 198mb. I tried the /reload ui tip again but this time the game crashed...but here's where it got wierd. I did not get the windows error message nor did I get the Blizzard window asking me to send the error to them. First time that hasn't happend with this error.
I hope I didn't waste my time in posting this and I hope your time wasn't wasted in reading it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt is somewhat clear that allocating memory in WoW is what is causing the crashes and addons that have a high rate of memory usage increase tends to be the ones that causes the crash, and that AI isn't the only such addon, but just one of the many possible ones. AI seems to be a common culprit only because it has the highest rate of memory use compared to every other addon.
Or simply (for those of us running embedded) the fact that AI is one of the first addons loaded alphabetically, so embedded libraries get attached to it...? So far, it's looking to me like a library issue (AceEvent-2.0 perhaps?) or a Blizzard bug.
I tend to agree.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIf what you said is really true, then disabling ArkInventory would have just pushed the problem to the next addon that embeds Ace2. However reports are contrary to this, that disabling AI more often than not tends to solve the problem by removing the enormous memory usage growth.
Indeed. I do not run with libraries embedded, and still chronically suffered from this issue while running ArkInventory. AI is EXTREMELY aggressive in terms of frequently allocating and almost immediately trashing large chunks of memory (5+MB) whenever something changes in your bags in order to create sorting tables to update the display. For some reason, Baggins doesn't seem to suffer from this issue.