Hey Guys,

There's tons of threads posted and lots of promising solutions. I have one that I've been testing for three days and have not had as much as lag spike when mousing over cogs. This works if you're willing to disable tooltips when you are anywhere a cog icon might show up.

You will need to create two macros, for "turn off tooltips" and "turn on tooltips".

Turn Off Tooltips
/script GameTooltip.Temphide = function() GameTooltip:Hide() end; GameTooltip:SetScript("OnShow", GameTooltip.Temphide);

Turn On Tooltips
/script GameTooltip:SetScript("OnShow", GameTooltip.Show);

This should get you through until the official fix comes down from Blizzard. Happy hunting!

---------------------------------------------------------
Update 10/26:

The patch released today, 4.0.1a lists the cog issues as being resolved. It seems to be working as intended now for most people, but there are still some lingering reports of cogs crashing clients.

PATCH 4.0.1a PATCH NOTES
http://forums.worldofwarcraft.com/thread.html?topicId=27387876237&sid=1

REPORTS ON COG FIX STATUS
http://forums.worldofwarcraft.com/thread.html?topicId=27401646913&sid=1

RECOMMENDED WORKAROUND ADDON
http://www.wowinterface.com/downloads/info18389-CrashProofTooltip.html

CURRENT KNOWN ISSUES STICKY
http://forums.worldofwarcraft.com/thread.html?topicId=27188060299&sid=1

REPORTED ISSUES SUMMARY THREAD
http://forums.worldofwarcraft.com/thread.html?topicId=27387366375&sid=1
---------------------------------------------------------
UPDATE 10/25:

Davidba has posted some good news!

---

Q u o t e:
UPDATE: We've made good progress on this issue and barring any unfortunate setbacks we should be able to roll out a fix fairly soon. Thanks to all of you who have been patient while we've worked on the problem. Thanks to the rest of you too; you may not be as patient, but your passion for our game is always respected and appreciated. Always.

On a personal note, I'll enjoy not being defeated by the Headless Horseman's pumpkin anymore! : )

---

---------------------------------------------------------
UPDATE 10/21:

Davidba has commented on Blizzards status on this issue.

---

Q u o t e:
I just wanted to pop in and confirm that Dev is working on this issue. I understand frustrations over the speed of resolution, but keep in mind that lot of problems simply can't be hotfixed. The worst reaction to a bug is to break five other things while recklessly fixing the first. One of my old favorites was a bugged monster in the barrens. The initial fix for it on the internal server broke the Illidan raid encounter in Outland. That may sound ridiculous from a non programmer's perspective (and it's certainly funny) but that's how code works.

I kept crashing on this same issue on my mage last night and had to use the script from earlier in the thread. Bear in mind that about 80% of us at Blizzard are playing WoW right along with you. We hate game issues from both perspectives, creator and player.

---

I'd say this is good that they are in the process of testing fixes and testing the implications of those fixes. Blizzard IS aware of this issue and they ARE in the process of fixing it -- it is not sitting idly on someone's todo list.
---------------------------------------------------------
UPDATE 10/20:

ADDONS
There is another addon out now that appears to be able to recreate those one-line tooltips so you don't see any change to your experience! I have not tested this out but check it out here:

http://www.wowinterface.com/downloads/info18389-CrashProofTooltip.html

---------------------------------------------------------
UPDATE 10/19 #2:

HEADLESS HORSEMAN EVENT

This workaround does not help crashes that occur that are not triggered by mousing over an item to interact with. It looks like there are some problems with instance servers currently, and you should direct any instance server crashing (or No Instance Servers are Available) messages to the Technical Support forum.

---------------------------------------------------------
UPDATE 10/19:

ADDITIONAL SOLUTIONS BEYOND THE MACRO
Looks like we might have this issue around another week! Reading a number of the posts going around, this does not appear to be the only issue in instances. From what I gather, the addon DBM may be causing instances to lag out without mousing over anything (on zoning-in or another players activity). I would suggest disabling DBM if you are still encountering issues after applying the macros or addon workaround.

HEADLESS HORSEMAN EVENT
Please see the section below BATTLEGROUND AND DUNGEON ISSUES If you are having disconnecting issues. I wanted a section on this just to discuss the other 50% of support posts, No loot in Event Bags: as the blues have

Thanks for the tip. Stickied.

Curiosity. Has anyone tried turning off Enhanced and Beginner Tooltips as a scriptless workaround?

Main Menu > Interface > Help: Uncheck Enhanced Tooltips; uncheck Beginner Tooltips.


I'd test it myself, but none of the computers around the office has the issue.

---

Q u o t e:
Hey good point, I might try that right now instead of the player fix and see if that works

---

Thanks, Zev! That would be great. : )

---

Q u o t e:
Negative, still crashes the client.

---

Shucks. Thanks for trying.

---

Q u o t e:
A little unsolicited advice from a fellow geek in the software industry: You need a wider variety of computers in your office.

---

Dev and QA have tons of different configurations; no worries there. I'm not at their location however. : )

I just wanted to pop in and confirm that Dev is working on this issue. I understand frustrations over the speed of resolution, but keep in mind that lot of problems simply can't be hotfixed. The worst reaction to a bug is to break five other things while recklessly fixing the first. One of my old favorites was a bugged monster in the barrens. The initial fix for it on the internal server broke the Illidan raid encounter in Outland. That may sound ridiculous from a non programmer's perspective (and it's certainly funny) but that's how code works.

I kept crashing on this same issue on my mage last night and had to use the script from earlier in the thread. Bear in mind that about 80% of us at Blizzard are playing WoW right along with you. We hate game issues from both perspectives, creator and player.

---

Q u o t e:
80%? Err, don't know why... but I expected it to be a lot higher than that.

---

It'll push higher when Cataclysm is released. And some folk love games but aren't big MMO players. Blizzard is still the only company I've ever worked for where most of the Human Resources department are avid gamers. : )

---

Q u o t e:
The update is appreciated, looking forward to the fix.

---

We are too. Losing to a pumpkin is embarrassing. : /

But yeah, I totally understand the desire to know that an issue is officially recognized and being worked on. I'm glad to provide that.

---

Q u o t e:
I remember a bug a couple years back where hunters that took a certain talent in a particular tree couldn't complete the Out With It achievement from Hallow's End because they could eat the Tricky Treats all day long and never puke.

---

Whoah! I'd forgotten about that! That was the Survival skill Sniper Training. That talent was involved in a couple odd bugs. ^_^

UPDATE: We've made good progress on this issue and barring any unfortunate setbacks we should be able to roll out a fix fairly soon. Thanks to all of you who have been patient while we've worked on the problem. Thanks to the rest of you too; you may not be as patient, but your passion for our game is always respected and appreciated. Always.

On a personal note, I'll enjoy not being defeated by the Headless Horseman's pumpkin anymore! : )

---

Q u o t e:
"The Cogwheel of Doom was merely a set-back!" - Davidba

That's how I read this. ^_^

---

Totally fair interpretation. : )

---

Q u o t e:
Being former military are you using the Navy sense of the term soon as in "soon-sometime before your enlistment ends" or the civilian version "soon-sometime in the next 15 days"?

---

Barring weirdness, the civilian version. Unlike a lot of forum issues that seem to be affecting a lot of WoW players but really aren't, this one genuinely is and has been a high-priority issue to resolve.

---

Q u o t e:
any chance on an explanation of the bug? some of us are interested in how wow ticks and what makes it suddenly stop.

---

While on the surface this is a great idea, the sheer crunch that the WoW team is under right now probably wouldn't make this feasible. However, if I hear a general explanation more compelling then "it was a UI thing" and I'm allowed to share then I'll definitely be glad to.