Been using aguf for awhile now with no problems whatsoever...downloaded the new AGUF version for pacth 2.1 and it seems to work fine, until i zone into a Battleground. Basically what happens is i load the battleground, get past the loading screen, and right when im in the battleground instance(can see my character, party members etc), everything just freezes up for 3 min+ before getting back to normal...and it only happens when I have aguf loaded. When I dont have aguf loaded, everythign works as it should...any ideas?
Oh and in order to isolate the addon/issue, i also tried deleting my wtf/wdb/cache/interface folders(putting wow in a pristine user state) and just used aguf by itself...same lag/freeze issue as described above, which only appears to occur when loading into battlegrounds, hoever i have not tried the same with 25 man instances...
Same happens for regular raids, spent nearly 10 minutes trying to make it work in Magtheridon's Lair this evening and in the end I had to result to just disabling it. Although it worked fine when I was logging in back in Shattrath yet still in the raid.
In any case something is seriously wrong with the raid frames.
Yep had this happen in Karazhan today. Didnt notice anything until I got that other bug with the blizzard target frame mentioned in another thread here and I tried to relog to clear that up.
When trying to log back in wow completely froze for a long time, not sure how long I waited exactly before I gave up, a minute or 2 at least. After having to close down wow with task manager and trying again 2 more times with the same result I disabled all addons and could log back without issues. I then tried enabling just my most essential addons (ag_uf being one of them ;)) this time I got back after maybe a minutes wait but noticed on the fubar performace monitor that my ui memory usage was 76mb and when checking the tooltip ag_uf alone was using 50mb, after forcing a garbage collection total memory usage dropped from 76 to 29mb. If it matters I have the raid frames disabled (using grid for that).
I ran into this same problem yesterday while trying to zone back in while in raid. The whole screen would just freeze and I had to turn the game off from the task manager. I solved it temporarily by telling the raid leader on VT to kick me from the raid and then I could login just fine then he would invite me back.
I'm still not sure if it was ag_unitframes that caused the problem. But me and several others in our raid had the same problem (all using ag_uf except 1 priest). I'm using grid, ora2, ag_uf, ct_core, ct_barmod, ct_bottombar, ct_mailmod, ct_viewport, KLHThreatMeter, pallypower, swstats.
I have also deleted the WTF and WDB folders and had a clear addon folder after the patch yesterday to be sure to not run into problems. Still I did. Also, I had the problem with the default blizzard frame appearing as described in a couple of other threads here.
This happened to my wife last night in karazhan, she got in once, then had to relog, every time subsequent to that with ag_uf enabled it would require a task manager kill of WoW or even a push button restart. With ag disabled it was fine.
I knew right from the start that it was ag_UF, and here's why: When I'd zone into a BG where there were already people in it, it would freeze, as stated above, but I noticed this: I have my settings (as most people) to hide the party frames when in a raid. During the time it was frozen, I could see both my party frame (with a bunch of "Unknowns" for names), AND the raid frame that had been generated so far. At the same time. So I wonder if it has something to do with that.
has not happened to me with my aguf setup at all, but has happened to 4 of my guilds aguf user's and to one of our(shudder)ct user's, however i was testing pitbull out for someone and it did happen with pitbull (but only when i swapped layouts), reports seem to indicate massive memory usage figures (7meg+) underload when joining a new battleground.