I was one of the people who had the microstutters on the live client. I found that AutoBar was doing some heavy memory growth since prepatch phase 2 on my system. It seems like there's a small memory leak somewhere that was affecting my client. I wish I had better info. Love the AddOn and am aware it could just be me.

How much memory are we talking about here? After you've been in the world for a minute or 2, it shouldn't be growing.

ok, when i enable "log performance" no events show up(aside from what pops on load). if i enable "log events" it spits out this, i get stutters roughly as it "shows new events" if i throttle events the stutter is just in time with that.

might be worth mentioning i'm running the game/addon off a mechanical hard-drive, could this be causing this issue?

i'll just add some screen shots of the other events just in case its helpful.
log memory
and this is "log events" and "log throttled events" with limit set to 5 seconds, this also causes a stutter every 5 seconds.

also if this format is not helpful and you need text let me know i'll find a way to get that.

I also get micro stutters the memory doesn't seem to increase past loading but when i use the add on "addon usage" which lets me see CPU usage and autobar shows as using alot more than anything else, could this be connected?

Ideally, once everything is loaded memory shouldn't keep growing and CPU usage should settle down. Some things to try to track down the problem:

1. Enable Log Performance in the settings. This will print an error if any bits of processing take too long. If you can tell me where these issues are, I can try to look into them.

2. You can disable "Allow SPELLS_CHANGED". This should lower CPU usage, but spell buttons may not always be 100% correct.

3. You can set the Throttle Event Limit to something like 0.25. This will make AutoBar ignore rapid notifications from WoW. Enabling Log Throttled Events will tell you if it's actually doing anything.

Is this still an issue? I removed some unnecessary logging, which should have helped at least a bit.

Closing due to lack of response.