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.
On the other hand, people have reported this problem without ever even having ArkInventory installed. So, AI doesn't seem to be the cause, it just accentuates the problem.
Not much. When wow crashes, the only thing you can do is send in crash reports via their reporting tool. Since there isn't really any specific steps in reproducing the problem, and only just a set of observed patterns (high memory usage), its difficult to track down something.
Not much. When wow crashes, the only thing you can do is send in crash reports via their reporting tool. Since there isn't really any specific steps in reproducing the problem, and only just a set of observed patterns (high memory usage), its difficult to track down something.
I think it may be more a pattern of frequent allocation and deallocation of memory by addons that is causing it, especially in conjunction with a high overall addon memory usage. I don't see it being fixed any time soon unless someone finds a way to reproduce it without any addons installed (good luck with that) or at least with only a single test addon specifically designed to replicate the issue.
[2008/04/25 12:22:54-3790-x17]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:382: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:272: in function `Show'
ArkInventory-2.27\ArkInventoryTooltip.lua:25: in function <...nterface\AddOns\ArkInventory\ArkInventoryTooltip.lua:9>
(tail call): ?:
<in C code>: ?
<in C code>: in function `SetHyperlinkCompareItem'
Interface\FrameXML\GameTooltip.lua:193: in function `GameTooltip_ShowCompareItem':
Blizzard_AuctionUI\Blizzard_AuctionUI.lua:1414: in function `AuctionFrameItem_OnEnter'
<string>:"*:OnUpdate":2: in function <[string "*:OnUpdate"]:1>
[2008/04/25 12:22:54-3790-x16]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:382: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:272: in function `Show'
ArkInventory-2.27\ArkInventoryTooltip.lua:25: in function <...nterface\AddOns\ArkInventory\ArkInventoryTooltip.lua:9>
(tail call): ?:
<in C code>: ?
<in C code>: in function `SetHyperlinkCompareItem'
Interface\FrameXML\GameTooltip.lua:190: in function `GameTooltip_ShowCompareItem':
Blizzard_AuctionUI\Blizzard_AuctionUI.lua:1414: in function `AuctionFrameItem_OnEnter'
<string>:"*:OnUpdate":2: in function <[string "*:OnUpdate"]:1>
Unrelated. Half the crashes were from a :GetRegions() call, which can potentially return a few hundred return arguments at the same time (one per texture and one per fontstring of the frame). While Lua can handle this easily, the WoW client itself might be restricted in some fashion.
Guillotine has posted a test addon on wowi: TooMuchData
to crash the client on purpose.. probably with the intention to help whoever is
trying to pinpoint the problem on Blizzard side find the issue.
It might be useful to know that the following script can also cause a Block too big error, but it won't crash WoW. Tables seem to have a maximum limit of somewhere between 8 MB and 16 MB in Lua in WoW.
/run i = 0; abc = {}; while true do i = i + 1; abc[i] = i; end
/dump i
That will print the value of i when the block too big occurs, and this number should be 2^19 + 1. This is just before array tables are doubled in size from 8 MB to 16 MB.
/run i = 0; abc = {}; while true do i = i + 1; abc[i*100] = i; end
would change the table to hash style, and the limit is lower, but still a power of 2. You can GC the table by running /run abc = nil after your experiment, your wow will not crash or anything.
This points to clues that the GetRegions() call somehow manipulates internal tables of frames and regions to return results, since the Block too big error is occurring inside it for many cases. When the call doesn't return, something in memory got corrupted and wow eventually crashes.
The hypothesis is that Cowtip is generating lots and lots of fontstrings and regions on GameTooltip and when it exceeds a certain limit, the error occurs.
I still haven't had any crashing problems since switching to baggins although I have had the game crawl a few times whilst raiding but forcing a garbage dump seems to cure it for a short while. Hopefully 2.4.2 will fix it but I am not holding my breath :D
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI think it may be more a pattern of frequent allocation and deallocation of memory by addons that is causing it, especially in conjunction with a high overall addon memory usage. I don't see it being fixed any time soon unless someone finds a way to reproduce it without any addons installed (good luck with that) or at least with only a single test addon specifically designed to replicate the issue.
Edit just saw hunters post suggesting the same thing sorry.
I agree also.
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:382: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:272: in function `Show'
ArkInventory-2.27\ArkInventoryTooltip.lua:25: in function <...nterface\AddOns\ArkInventory\ArkInventoryTooltip.lua:9>
(tail call): ?:
<in C code>: ?
<in C code>: in function `SetHyperlinkCompareItem'
Interface\FrameXML\GameTooltip.lua:193: in function `GameTooltip_ShowCompareItem':
Blizzard_AuctionUI\Blizzard_AuctionUI.lua:1414: in function `AuctionFrameItem_OnEnter'
<string>:"*:OnUpdate":2: in function <[string "*:OnUpdate"]:1>
[2008/04/25 12:22:54-3790-x16]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:382: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:272: in function `Show'
ArkInventory-2.27\ArkInventoryTooltip.lua:25: in function <...nterface\AddOns\ArkInventory\ArkInventoryTooltip.lua:9>
(tail call): ?:
<in C code>: ?
<in C code>: in function `SetHyperlinkCompareItem'
Interface\FrameXML\GameTooltip.lua:190: in function `GameTooltip_ShowCompareItem':
Blizzard_AuctionUI\Blizzard_AuctionUI.lua:1414: in function `AuctionFrameItem_OnEnter'
<string>:"*:OnUpdate":2: in function <[string "*:OnUpdate"]:1>
http://pastey.net/87000
anybody getting any crashes without an ace3 mod loaded?
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumto crash the client on purpose.. probably with the intention to help whoever is
trying to pinpoint the problem on Blizzard side find the issue.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium/run i = 0; abc = {}; while true do i = i + 1; abc[i] = i; end /dump iThat will print the value of i when the block too big occurs, and this number should be 2^19 + 1. This is just before array tables are doubled in size from 8 MB to 16 MB.
/run i = 0; abc = {}; while true do i = i + 1; abc[i*100] = i; endwould change the table to hash style, and the limit is lower, but still a power of 2. You can GC the table by running /run abc = nil after your experiment, your wow will not crash or anything.
This points to clues that the GetRegions() call somehow manipulates internal tables of frames and regions to return results, since the Block too big error is occurring inside it for many cases. When the call doesn't return, something in memory got corrupted and wow eventually crashes.
The hypothesis is that Cowtip is generating lots and lots of fontstrings and regions on GameTooltip and when it exceeds a certain limit, the error occurs.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumis there any solution for this? I am still suffering from this issue which seems to be more often when raiding (up to 3 to 4 times within 3 hours).
Kind regards
X-buZZ
Is this in 2.4.2? I was hoping they'd ninja fix it.