AV 132 critical crash - possible cause

[Proctologist]

Yada-yada, let's get to it shall we.
(and I don't know if this has been stated already)

First of all we've confirmed through several AVs that the 132 error is a result of someone opening the scoreboard, and it's random but if both teams are full ~40v40 it causes some kind of loop and causes someone or several people to get this 132 error... A memory leak.

One confirmation of this is that throughout these AVs someone would open the scoreboard on a timed... ''Click'' and each time there were some people INSTANTLY getting the critical error.
How? Well it's the result of the following;

Did some quick search and found this code
void BattleGroundMgr::BuildPvpLogDataPacket(WorldPacket *data, BattleGround *bg)

And this is what keeps looping

*data << (uint32)(bg->GetPlayerScoresSize());

for(BattleGround::BattleGroundScoreMap::const_iterator itr = bg->GetPlayerScoresBegin(); itr != bg->GetPlayerScoresEnd(); ++itr)
{


What can we as players do?

NEVER, EVER, FOREVER OPEN SCOREBOARD!
Because it queries the server for the statistics and runs some occasional loop that causes the errors.

[SnowFlakes]

Anyone that gets error 132 should be banned for exploiting the leaderboards.

[Codeine]

Soon as I join AV i get critical errors, disable all addons and trying again doesn't work just repeated crit errors soon as you log in while inside AV.

Anyone else have the same thing?

[Lobreeze]

Soon as I join AV i get critical errors, disable all addons and trying again doesn't work just repeated crit errors soon as you log in while inside AV.

Anyone else have the same thing?

Yes.