WowAce

------------------------------------------------------------------------
r49 | funkydude | 2012-11-15 01:34:51 +0000 (Thu, 15 Nov 2012) | 1 line
Changed paths:
   A /tags/v5.0.5.2 (from /trunk:48)

Tagging as v5.0.5.2
------------------------------------------------------------------------
r48 | funkydude | 2012-11-15 01:31:21 +0000 (Thu, 15 Nov 2012) | 1 line
Changed paths:
   M /trunk/StatBlock_Memory.lua
   M /trunk/StatBlock_Memory.toc

Remove a pointless if statement that permanently blocks updating for users over 105 ms.
------------------------------------------------------------------------
r46 | funkydude | 2012-11-15 01:14:32 +0000 (Thu, 15 Nov 2012) | 1 line
Changed paths:
   M /trunk/StatBlock_Memory.lua

newline fix
------------------------------------------------------------------------
r45 | funkydude | 2012-11-15 00:52:48 +0000 (Thu, 15 Nov 2012) | 1 line
Changed paths:
   M /trunk/StatBlock_Memory.lua

Actually show how long it took to process all addons in the tooltip and add a warning to it explaining it will disable itself in combat if over 105 ms.
------------------------------------------------------------------------
r44 | funkydude | 2012-11-15 00:12:07 +0000 (Thu, 15 Nov 2012) | 1 line
Changed paths:
   M /trunk/StatBlock_Memory.lua
   M /trunk/StatBlock_Memory.toc

Some users run so many addon's that Blizz's "UpdateAddOnMemoryUsage()" takes too long and triggers a script too long error. We now detect the time it takes to process this function using debugprofilestop() and kill updating memory usage in combat for users that take over 105 ms to finish. For comparisons sake, it takes me 10-20 ms.
------------------------------------------------------------------------