WowAce

What version of Grid2 are you using (Version is displayed in General/About Tab)?

2.1.1 Wrath

What game client version, classic or retail, windows or mac and language are you using?

Classic

What steps will reproduce the problem?

Pulling a boss in a 25-man raid.

  
Did you try having Grid2 as the only enabled addon and everything else disabled?

Yes

Was it working in a previous version? If yes, which was the last good one?

Grid2 worked fine in Classic TBC. I guess Blizzard changed something about their API(?) since Wrath and a lot of addons are heavy on resources. That's all I know.

Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).

I don't.

Please provide any additional information below.

I was using Grid2 back in OG Wrath, and I continue to love it now, preferring its simplicity over Vuhdo and Healbot. But I have to settle for Blizzard Raid Frames. I disabled all of my addons in Naxx25 and would get a mild 10-15 fps drop during boss fights. When I enabled Grid2, I'd get a 30-35 fps drop. The same was true for other raid frame addons, except Blizzard's stock raid frames. I don't know what they're doing, but I can tell you that I was running both Healbot and Grid2 at the same time in TBC just fine. Now just one of them kills my fps. If you have any idea what indicator might be causing this, maybe incoming heals or a threat measurement, let me know. I'd come back to Grid2 in a heartbeat if the stutter wasn't so bad.

Try disabling LibHealComm library.

1. Goto Statuses / Health&Heals / heals-incoming

2. In the "Heals Api" option, select "Blizzard API" instead of "LibHealComm-4"

Unfortunatelly changing this option is not enough to full disable libhealcomm, so if the issue is not fixed after this,  you must remove or rename the libhealcom library.

3. Goto:  Wow Classic Folder/Interface/Addons/Grid2/Libs

4. Remove or rename the "LibHealComm-4.0" Folder

After removing this library  you will get a lua error on game start up due to the missing LibHealComm-4.0 library, but the errror is harmless, Grid2 should work fine after the error.

You should check others addons too, because some others addons can install and enable the libhealcom-4 library too, so if another addon includes libhealcomm you must disable this addon too.

Unfortunatelly Blizzard API is very limited so without HealComm a lot of incoming heals are not displayed (specially HOTs).

Please, report back if this fix the issue.

You can update Grid2 to 2.1.2-beta-wrath. In this version LibHealComm-4 has been removed. Unfortunatelly this library does not perform well on Wotlk.

Players not experiencing performance issues can still use LibHealComm-4 heals information but they should install libhealcom-4 addon separately (It's available on curseforge).

Thank you very much for the reply, and I apologize for a late follow-up. I took a much needed break from addon problem-solving this week. It's our second week of clearing Ulduar, and while the default Blizzard raid frames are adequate, they leave so much to be desired. I'll test out this solution next raid night.

Question: How do I tell if an addon uses LibHealComm? I'd love to go through my addons and check.

You can Update to 2.1.3-wrath (instead of  2.1.2-beta).

If you want to see if some other addon is using libhealcom, open Grid2 configuration (version 2.1.3-wrath), goto

Statuses/health&heals/heals-incoming

In the  Heals API option if you can select LibHealCom-4 this means that another addon in your system includes libhealcom.

Then you can  look for "LibHealComm-4.0" folders inside wow addon directory.

"C:\Program Files (x86)\World of Warcraft\_classic_\Interface\AddOns"

on the top right search edit box type:

LibHealCom

This problem seems to be resolved, and I'm happy to be back with Grid2! Although I still have some FPS drop in 25s, it's a lot less than before. I wish I could completely avoid this, but I'm living with it. I think your removal of HealComm helped a lot. I might try to use the Blizzard API for incoming heals, as it's important to see that. But I've been living without that for a while too. Thanks a lot of for assisting me!