Edit: Disabling Advanced Combat Logging appears to resolve the issue. MAKE SURE you completely restart the game after doing so.
Then test in a random heroic or on a stealth class by going into a dungeon and pulling a boss before specific queueing heroics to make sure this resolved the issue for you.
Starting today, myself, many guild mates, and random players around discord are getting a fatal error that is crashing the game when engaging bosses in dungeons. Some sort of crazy memory leak issue or something. Is there an ETA on a fix for this?
Myself and a few other that this is happening to have tried that. Also deleted Cache folder etc. The issue still persists. As mentioned above, it appears to only be happening on boss pull in dungeons.
Yea, this just happened to me 2x in Stormstout Brewery. Eventually got kicked b/c the client crashed on boss pull, and what’s more annoyign is – i can’t requeue specific for it b/c now I’m locked hah
Disabling the Advanced combat logging under options - network, fixed my issue as well. So far no more crashes after pulling a boss 6 times now. Also, this has ONLY happened to me within the last hour or so and only when a boss is pulled. Trash mobs/open world mobs have been fine.
Clarification for new people coming in: #1 Disable advanced combat logging (ACL (I also exited out of warcraft logs app, unsure if related at all)) #2 Hard restart the game #3 Test on an alt that has stealth is you can. I ran to Jade serpent normal solo and pulled the boss multiple times to make sure it was actually good to go. This is to avoid the deserter debuff possibility as you trouble shoot.
#1 Disable advanced combat logging (ACL (I also exited out of warcraft logs app, unsure if related at all)) #2 Hard restart the game #3 Test on an alt that has stealth is you can. I ran to Jade serpent normal solo and pulled the boss multiple times to make sure it was actually good to go. This is to avoid the deserter debuff possibility as you trouble shoot.