Added cop's fix to my SAA code, after the servers come up and I've had a chance to test it I'll report back with performance changes/any other relevant info.

I'm not expecting a large performance hit. Everyone's probably already running multiple mods that hook UNIT_AURA (buff mods, unit frames, etc.).

No, neither am I, but I'd prefer confirmation before I make it official.

Caused a serious performance hit for me in testing whenever I put a hot on myself. It would hiccup.

No noticeable performance hit vs target dummies. Didn't get a chance to test it in a raid setting, if anything is different there I'll update this post.

I did not notice a performance change, I even applied hots to myself and had other druids do it as well (in a raid). However, I was capturing a lot of errors with squawk and awe, unfortunately I did not have time to look into it. I will get more info on that tonight though.

I had good luck with the fix that you posted, but was unable to test it in a raid environment because our raid and instance servers went down the instant i finished fixing my interface. Against a target dummy it was using about 1Mb of memory, which is more than it was using before, but less than a lot of other timer mods.

If you plan on editing your lua file be sure you have the most updated version of Squawk And Awe. If you do not have the most updated version you will get a large number of error messages.

Thanks for getting a fix out there so fast guys. I really didn't want to have to find and adjust a new moonkin timer when i enjoy using this one so much.

I tried making the modifications last night, but was not able to get it to work. I'm sure I did something wrong, but I am not experianced with Lua and WoW addons at all. Could you guys upload a updated version on WoWInterface?

Based on the feedback in this thread, I'll probably upload it sometime today.

Shibby, do you know what memory footprint it was using before? 1MB is a lot, the changes aren't storing any new data, and I can't imagine that adding an event handler consumes that much memory. Not that it's a huge issue for it to be that large in principle, but I don't like confusing results.

Beef, I have no idea what would cause it to hiccup on just HoTs, does it hiccup on the spells it's supposed to track as well?

I was able to run it in raid last night, but found that the addon would seem to lockup in combat tracking my trinkets.

At least the error I was getting is as shown below and disabling tracking of trinkets resolved my issue. No other problems were observed.


"SquawkAndAwe-SquawkAndAwe v1.3.3 (r1)\\SquawkAndAwe.lua:1247: attempt to concatenate field 'itemname' (a nil value)\nSquawkAndAwe-SquawkAndAwe v1.3.3 (r1)\\SquawkAndAwe.lua:895: in function <Interface\\AddOns\\SquawkAndAwe\\SquawkAndAwe.lua:894>\n\n ---",

I have no idea where it was running beforehand.

My testing that came up with 1 meg consisted of me mousing over my addon memory when I was spamming on a target dummy trying to decide if my interface was working, so take that number with a grain of salt.

I will try to keep track of it tonight if the instance servers are up.