I have a problem with the mod on two seperate computers. I've tried reinstalling the mod, though I'm not sure if it was the same version. It still doesn't fix the problem, in any case.
I can't pull up data on myself. You know the bars window? I can see myself, but I cannot "click for more details". I can click on any other people and am able to read further in depth. But when I click on myself, the game freezes.
It actually freezes my entire computer. The sound keeps going and I'm able to move my mouse, but the computer locks in. Nothing responds, I cannot minimize the window, and ctrl+alt+del does nothing. Whenever this happens, the only way I can continue is to hold the "on/off" button on my computer box manually until the power cuts off, and restart the computer this way.
This problem occurs on both computers, in seperate houses and networks entirely. Any clue as to why this is and/or how to fix it? Sorry if someone has already posted something about this.
I just had a problem with Recount not recording a raid member's death. She died right next to me from a Icebolt on Rage Winterchill but there was no death listed for her when I checked after the fight.
At what point in time does it make sense to nuke a 101 page thread and start a new one? Maybe starting the thread with a collection of known and outstanding issues/questions from the previous monster thread?
I'm having a random situation were Recount/Ace3 takes up an awful lot of CPU and in practise freezes my wow for anything between 2 seconds to a minute or so. Average is about 5 seconds.
I first got the result for Recount and Omen, but after removing the Ace3 embedded libs and using Ace3 standalone, it showed up as Ace3 and Recount.
The other 50 or so addons: 0.9%
I can't reliably reproduce this, but when it happens it is relatively common that I have been on a raid the day before and not reset the Recount data. I then use my pet and go and fill up soul shards. After a mob dies, I sometimes get a freeze for 2-5 seconds and Ace3 and Recount have during the freeze used up hundreds if not thousands times more CPU than usual in a raid.
I have split Ace3 into its components to see if I narrow it down which Ace3 component it is that is getting hammered. I have not been able to reproduce this since the split though. I guess it is a bug in Recount that calls something in Ace3 an awful lot of times though.
Splitting Ace3 into components shows that it is AceTimer-3.0 that takes up a lot of CPU there.
AddonManager shows about the same amount of CPU on AceTimer as on Recount, but the number don't match Expo. AM shows about 17000 ms on AceTimer and 17000 on Recount, but since that roughly adds up to what Expo says on Recount I guess that is just down to how they allocate the time to a lib.
Expo on Recount shows for about a minute measuring interval when wow hangs completely (Real time and killing a single mob):
:FreeTable - 34.294 sec - called 3968 times - time/call 8.6 ms
:GetTable - 0.746 sec - 1246 times - 0.599 ms per call
:ResetFightData - 0.033 s - 49 times - 0.673 ms per call
Wow hangs about half a second after the mob dies.
When resetting data in Recount the problem goes away immediately. Then the top method in Recount is :TimeTick at 0.006 ms.
Again this happened when I had been on a raid the day before and not resetting the data.
Tried deleting Savedvariables? (WTF, Account, [Accountname]).
Then press CTRL+F and search for Recount, delete everything you find.
Done and done (the first time). Did not remedy the issue.
This isn't related to missing death logs. Usually those are caused by the death event simply not registering (and this is confirmed by the combat log). My problem is the death logs are just wrong (and sometimes for a completely different person).
I'll keep my eye out for this one. I have noticed that under some circumstances there are multiple death log entries, but never wrong attributions. If you find a way to reliably reproduce this let me know.