Blue Screen with wow client : memory allocation error

Kindersama · 08-19-2009

Hello,

I have this bugs with an addon (memory allocation error), but I don't know which one causes this. It only happens during raids after a certain numbers of encounters/tries on bosses (we are on Mimiron 10

).
I've got the "fatality" sound of bugrabber/bugsack and I can't cast any spells and it's disturbing for a healer

Every time it's happening, I have to reload my interface (/rl) and everything is fine again, but the bug messages are gone. Tonight I could have copy/paste the messages before client crash and the blue screen :

Code:

[2009/08/18 23:29:58-2561-x6]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:423: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:304: in function <Interface\AddOns\CowTip\Appearance\Appearance.lua:299>
<in C code>: in function `SetUnitBuff'
Outfitter-4.7.4\Outfitter.lua:4313: in function `GetBuffTooltipText'
Outfitter-4.7.4\Outfitter.lua:4296: in function `GetPlayerAuraStates'
Outfitter-4.7.4\Outfitter.lua:4364: in function `UpdateAuraStates'
Outfitter-4.7.4\Outfitter.lua:4356: in function <Interface\AddOns\Outfitter\Outfitter.lua:4351>
<in C code>: in function `pcall'
Outfitter-4.7.4\MCEventLib.lua:212: in function `DispatchEvent'
Outfitter-4.7.4\MCEventLib.lua:65: in function <Interface\AddOns\Outfitter\MCEventLib.lua:65>

Code:

[2009/08/18 23:29:59-2561-x14]: memory allocation error: block too big:
<in C code>: in function `SetScript'
Interface\FrameXML\UIParent.lua:2370: in function `UIFrameFade':
Interface\FrameXML\UIParent.lua:2390: in function `UIFrameFadeOut':
Interface\FrameXML\FloatingChatFrame.lua:865: in function `FCF_OnUpdate':
<string>:"*:OnUpdate":1: in function <[string "*:OnUpdate"]:1>

  ---

Code:

[2009/08/18 23:29:59-2561-x8]: memory allocation error: block too big:
<in C code>: in function `SetAttribute'
Interface\FrameXML\SecureHandlers.lua:734: in function <Interface\FrameXML\SecureHandlers.lua:723>:
(tail call): ?:
Bartender4-3\ActionButton.lua:283: in function <Interface\AddOns\Bartender4\ActionButton.lua:275>
<in C code>: in function `ActionButton_Update'
Interface\FrameXML\ActionButton.lua:360: in function `ActionButton_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

  ---

Code:

[2009/08/18 23:29:59-2561-x1]: memory allocation error: block too big:
<in C code>: in function `SetScript'
Interface\FrameXML\UIParent.lua:2370: in function `UIFrameFade':
Interface\FrameXML\UIParent.lua:2390: in function `UIFrameFadeOut':
Interface\FrameXML\FloatingChatFrame.lua:869: in function `FCF_OnUpdate':
<string>:"*:OnUpdate":1: in function <[string "*:OnUpdate"]:1>

  ---

Code:

[2009/08/18 23:28:44-2561-x1]: DBM-Core\DBM-Core.lua:1565: bad argument #1 to 'min' (number expected, got boolean)
DBM-Core\DBM-Core.lua:1565: in function `EndCombat'
DBM-Core\DBM-Core.lua:1597: in function `OnMobKill'
DBM-Core\DBM-Core.lua:1604: in function `?'
DBM-Core\DBM-Core.lua:213: in function <Interface\AddOns\DBM-Core\DBM-Core.lua:209>
(tail call): ?:
DBM-Core\DBM-Core.lua:213: in function <Interface\AddOns\DBM-Core\DBM-Core.lua:209>

  ---

Code:

[2009/08/18 23:31:40-2561-x1]: memory allocation error: block too big:
<in C code>: in function `GetRegions'
CowTip-r68121\Appearance\Appearance.lua:423: in function `SetFont'
CowTip-r68121\Appearance\Appearance.lua:313: in function `Show'
Altoholic-v3.2.001c\Altoholic.lua:1145: in function `ShowWidgetTooltip'
<string>:"*:OnEnter":1: in function <[string "*:OnEnter"]:1>

  ---

Can anyone help me finding the addon causing this annoying crash, in order to fill a ticket and correct this bug ? Thanks

Farmbuyer · 08-19-2009

DBM is an unrelated problem; it's already been reported and acknowledged by the DBM authors, now we're just waiting for them to copy&paste the fix everywhere and spin a new release.

edit: nvm, Phanx nailed it

Phanx · 08-19-2009

The "memory allocation error: block too big" errors/crashes are a known and long-standing problem with CowTip. There are dozens of threads about this problem, dating back well over a year. The solution has generally been "switch to another tooltip addon".

Kindersama · 08-19-2009

The memory allocation errors occur inside the game. The client crash when I reload the interface.

Message error when the client crashes :

Quote:

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Users\Public\Games\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:005327DF

The instruction at "0x005327DF" referenced memory at "0x0008500C".
The memory could not be "written".

Recount is configured to autodelete time data, so on each try on Mimiron, recount was cleared.
I also thing that this is a coding bug, but which addon is bugged ? cowtip ? altoholic ? bartender ? outfitter?

addon listing from the client crash :

Quote:

WoWBuild: 10192
Realm: Rashgarroth [80.239.149.48:3724]
Local Zone: Vault of Archavon
Local Player: Quinne, 0380000002555CBF, (-221.627,-273.917,91.6061)
Total lua memory: 109504KB
Add Ons: AckisRecipeList ACP ag_Extras ag_UnitFrames Altoholic Atlas Atlas_Battlegrounds Atlas_DungeonLocs Atlas_OutdoorRaids Atlas_Transportation AtlasLoot AtlasLoot_WrathoftheLichKing AtlasLootFu AutoBar Bartender4 BigBrother Broker2FuBar Broker_TradeCooldowns !BugGrabber BugSack ButtonFacade Chinchilla ClassLoot ClassTimer CloseUp ControlFreak CooldownTimers3 Cosplay CowTip CT_ExpenseHistory CurseProfiler DataStore DataStore_Achievements DataStore_Auctions DataStore_Characters DataStore_Containers DataStore_Crafts DataStore_Currencies DataStore_Inventory DataStore_Mails DataStore_Pets DataStore_Quests DataStore_Reputations DataStore_Skills DataStore_Spells DataStore_Stats DataStore_Talents DBM-Sarth-ShadowFissureWarn Decursive Digits DrDamage DualSpeccer ElkBuffBars FuBar_BagFu FuBar_DurabilityFu FuBar_FactionsFu FuBar_FriendsFu FuBar_GroupFu FuBar_GuildFu FuBar_InstanceInfoFu FuBar_LocationFu FuBar_MoneyFu FuBar_PerformanceFu FuBar_TopScoreFu FuBar Grid GridStatusHealingReduced GridAutoFrameSize GridIndicatorCornerPlus GridManaBars GridSideIndicators GridStatusHots GridStatusThreat HeadCount LoggerHead MikScrollingBattleText Minimalist Omen OmniCC OneBag3 OneBank3 oRA2_Optional oRA2_Participant oRA2 Outfitter PallyPower Pawn Postal PowerAuras Prat-3.0 Prat-3.0_Libraries Procodile Quartz Quartz_Buff Quartz_Flight Quartz_Focus Quartz_GCD Quartz_Interrupt Quartz_Latency Quartz_Mirror Quartz_Pet Quartz_Player Quartz_Range Quartz_Swing Quartz_Target Quartz_Timer Quartz_Tradeskill RatingBuster Recount SHIT Skinner SpamSentry Talented Talented_SpecTabs tekKompare tekticles +Wowhead_Looter XLootMaster XLootMonitor XLoot XRS DBM-Core DBM-LDB DBM-SpellTimers DBM-Battlegrounds DBM-BurningCrusade DBM-ChamberOfAspects DBM-Forte DBM-Naxx

Kindersama · 08-19-2009

Quote:

Originally Posted by Phanx

The "memory allocation error: block too big" errors/crashes are a known and long-standing problem with CowTip. There are dozens of threads about this problem, dating back well over a year. The solution has generally been "switch to another tooltip addon".

that's what I thought... Thanks

MegaManJuno · 08-19-2009

Quote:

Originally Posted by Phanx

The "memory allocation error: block too big" errors/crashes are a known and long-standing problem with CowTip. There are dozens of threads about this problem, dating back well over a year. The solution has generally been "switch to another tooltip addon".

CowTip apparently wasn't the only one triggering it, because I used to see this as well (as I've stated before) and never touched CowTip. /shrug

Farook · 08-19-2009

http://forums.wowace.com/showthread.php?t=12076
http://forums.wowace.com/showthread.php?t=14666

fyrye · 08-23-2009

Strange, as I have run CowTip for a long time and haven't this issue at least not reoccurring. And have run 12+ hours straight. Though I have a fairly high end PC for WoW's standards.
I raid very frequently as well do BGs/Arenas/Questing (Level+Dailies)
Considering it only happens while in a raid, it would more than likely be tied into a thread running while in the raid. A conflict of resources so to speak.
Addon A) Starts Event
Addon B) Hooks the same event
Addon C) Displays Information on event start

An issue can occur where the system is stressed where Addon A is still processing when Addon C tries to display information on Addon B which is Hooking Addon A, causing the Memory exception Access Denied.

Example:
During the fight DBM fires an event based off the combat log, at the same time, recount deletes timed data as it also is gathering information from the combat log, and at the same time you hover over a spell or item to click it which causes cowtip to populate its tooltip frame.

HunterZ · 08-27-2009

Uh oh, "block too big" is back...dun dun dunnnn

Quote:

Originally Posted by Farook

http://forums.wowace.com/showthread.php?t=12076
http://forums.wowace.com/showthread.php?t=14666

Thanks for digging up the links to those, I felt compelled to but was dreading the time and effort it would take

Goncyn · 08-27-2009

I got the "block too big" error sometimes upon logging back in after I had logged out with a HUGE amount of data recorded in Recount. That was one of the reasons I decided to switch to Skada.

08-19-2009	#2
Farmbuyer Hero Member Join Date: Feb 2005 Posts: 537	Re: Blue Screen with wow client : memory allocation error DBM is an unrelated problem; it's already been reported and acknowledged by the DBM authors, now we're just waiting for them to copy&paste the fix everywhere and spin a new release. edit: nvm, Phanx nailed it Last edited by Farmbuyer; 08-19-2009 at 02:12 AM.

08-19-2009	#3
Phanx Seal Cub Clubbing Club Join Date: May 2005 Posts: 5,576	Re: Blue Screen with wow client : memory allocation error The "memory allocation error: block too big" errors/crashes are a known and long-standing problem with CowTip. There are dozens of threads about this problem, dating back well over a year. The solution has generally been "switch to another tooltip addon". __________________ Author/maintainer of Grid, PhanxChat, AnkhUp, OnScreenHealth, ShieldsUp, and others.

08-19-2009	#7
Farook Hero Member Join Date: Oct 2005 Posts: 917	Re: Blue Screen with wow client : memory allocation error http://forums.wowace.com/showthread.php?t=12076 http://forums.wowace.com/showthread.php?t=14666 __________________

08-23-2009	#8
fyrye Full Member Join Date: Jan 2008 Posts: 129	Re: Blue Screen with wow client : memory allocation error Strange, as I have run CowTip for a long time and haven't this issue at least not reoccurring. And have run 12+ hours straight. Though I have a fairly high end PC for WoW's standards. I raid very frequently as well do BGs/Arenas/Questing (Level+Dailies) Considering it only happens while in a raid, it would more than likely be tied into a thread running while in the raid. A conflict of resources so to speak. Addon A) Starts Event Addon B) Hooks the same event Addon C) Displays Information on event start An issue can occur where the system is stressed where Addon A is still processing when Addon C tries to display information on Addon B which is Hooking Addon A, causing the Memory exception Access Denied. Example: During the fight DBM fires an event based off the combat log, at the same time, recount deletes timed data as it also is gathering information from the combat log, and at the same time you hover over a spell or item to click it which causes cowtip to populate its tooltip frame.

08-27-2009	#10
Goncyn Member Join Date: Mar 2005 Posts: 47	Re: Blue Screen with wow client : memory allocation error I got the "block too big" error sometimes upon logging back in after I had logged out with a HUGE amount of data recorded in Recount. That was one of the reasons I decided to switch to Skada.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)