Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
today 2.4.2 has arrived for the german gamers. We had a Kara raid and the error came up for me two times within 3 hours. So this is definitivly NOT fixed with the new patch :(
Was playing my main for awhile (none of my alts) and it was crashing quite a bit, but in the last week it seemed to be stable.Today I started playing an alt,crashed.
Was playing my main for awhile (none of my alts) and it was crashing quite a bit, but in the last week it seemed to be stable.Today I started playing an alt,crashed.
Does your alt run any addons that your main doesn't?
Happened again last night for the first time in quite a while. My addon memory usage was reported at right around 145MB, which seems to be the magic number for me. No addon was using more than 5MB though, and nothing was using anything higher than normal, so I don't understand what would be using over 60MB more than the usage reported after a login or reloadui. I did frequent manual garbage collections (via performancefu) as the number climbed, but they didn't reduce the memory usage by more than a couple MB. It's almost like something is creating garbage that the LUA engine doesn't know how to collect but isn't able to attribute to an addon.
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)
I stopped using any Ace mod using Cowtip or not up to date with the current version of WoW and I have not seen this issue since. The down side to this is I am unable to use Arkinventory, Skinner or Sorren's Timers.
I continue to use all my addons. I experienced the issue pre 2.4.2. Have not experienced since. I've also updated several of my addons as well.
I have had crashes, but I have not seen the error in the title of this thread thrown since 2.4.2.
I have, but I've tried to both slim down my UI on my raiding main and reload my UI periodically to reset memory usage to the baseline startup value, so it doesn't happen often.
i did some intense testing during the last weeks.
I came to the the conclusion that ArkInventory is causing the error for ME.
My tests:
1. Raiding (ArkInventory enabled)
Kara raiding time. The error came up nearly every hour. I went to Kara 4 times and with ArkInventory enabled the error could be reproduced very reliable each time.
2. Questing (ArkInventory enabled)
At two days i had the time to complete all 25 daily quests. Lasted about 5 hours. At the first day the error came up 2 times. Not as frequent as when going to Kara but it was there. At day 2 the error came up one time only but it was there.
3. Raiding (Combuctor enabled)
3 times Kara raiding again. AI disabled, Cumbuctor enabled. No errors at all.
4. Questing (Combuctor enabled)
3 days of heavy daily questing again. No errors.
So for my setup AI is the causing the annoying issue. I can remember that it appeared for the first time since i had update to the AI version introducing the mailbox and current gear support. The bad thing about that is that i REALLY love this addon. No other bag addon has to offer so much nice features.
I hope that the author of AI can take a closer look at this. Perhaps its not the addon itself but a library it uses.
Kind regards
X-buZZ
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorNot sure why you would need to without addons, but /script collectgarbage("collect")
Thanks!
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumtoday 2.4.2 has arrived for the german gamers. We had a Kara raid and the error came up for me two times within 3 hours. So this is definitivly NOT fixed with the new patch :(
o_O What does that have to do with this thread?
Was playing my main for awhile (none of my alts) and it was crashing quite a bit, but in the last week it seemed to be stable.Today I started playing an alt,crashed.
Does your alt run any addons that your main doesn't?
Had it happen last night, so definitely not fixed with the patch although it has been more stable.
Ive only had it happen while groupped, never solo. Occurs most often in raid but have had it while duoing too.
nope been running baggins for a month or so now
[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.
I stopped using any Ace mod using Cowtip or not up to date with the current version of WoW and I have not seen this issue since. The down side to this is I am unable to use Arkinventory, Skinner or Sorren's Timers.
I have had crashes, but I have not seen the error in the title of this thread thrown since 2.4.2.
I have, but I've tried to both slim down my UI on my raiding main and reload my UI periodically to reset memory usage to the baseline startup value, so it doesn't happen often.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi did some intense testing during the last weeks.
I came to the the conclusion that ArkInventory is causing the error for ME.
My tests:
1. Raiding (ArkInventory enabled)
Kara raiding time. The error came up nearly every hour. I went to Kara 4 times and with ArkInventory enabled the error could be reproduced very reliable each time.
2. Questing (ArkInventory enabled)
At two days i had the time to complete all 25 daily quests. Lasted about 5 hours. At the first day the error came up 2 times. Not as frequent as when going to Kara but it was there. At day 2 the error came up one time only but it was there.
3. Raiding (Combuctor enabled)
3 times Kara raiding again. AI disabled, Cumbuctor enabled. No errors at all.
4. Questing (Combuctor enabled)
3 days of heavy daily questing again. No errors.
So for my setup AI is the causing the annoying issue. I can remember that it appeared for the first time since i had update to the AI version introducing the mailbox and current gear support. The bad thing about that is that i REALLY love this addon. No other bag addon has to offer so much nice features.
I hope that the author of AI can take a closer look at this. Perhaps its not the addon itself but a library it uses.
Kind regards
X-buZZ