Hey again all,
We just synced again with the devs and wanted to let you know that we’re still working on this - emphasis on actively working. While I can’t share exact specifics as to what has been done thus far, I can at least give you all a bit of a peek behind the curtain, as we feel you deserve that right now. Hopefully this post at least gives you a bit of insight as to what’s been going on over the past couple weeks. Before I get too deep into it - I wanted to clarify something.
This investigation is for players with Intel graphics cards. Some of the players posting in this thread have other graphics chips, and your crashes may not be related to what we are investigating at all. If you are using a Mac with a Nvidia or AMD graphics card, we recommend that you try troubleshooting the crash instead of waiting on updates, as there are several things that cause crashes other than this specific bug. Since the bug has been tracked down to happening with Intel machines, what we do to fix this is unlikely to have any impact on crashes for anybody who uses a different GPU. I’ve updated the thread title to clarify this.
With that out of the way, let’s talk some about where we were earlier this month, and where we are now. When we got the initial report of this bug, we had our Quality Assurance folks look into it, and they helped us find some scenarios where the crashes happened. That was what we tried to fix with the hotfix we mentioned above. Unfortunately, the problem was deeper than what we initially had identified. On behalf of all of us at Blizzard I wanted to apologize that we set kind of a bad expectation earlier in the thread. We thought we fixed the problem, we were wrong, and so we went back to the drawing board.
Without going into the complete technical details, we’ve spent more time reproducing things with Quality Assurance, found more problems, and tried more code tweaks to fix the things we’ve found since the initial hotfix attempts. None of our tweaks, however, have been successful enough (as indicated by the thread) which is why we aren’t out here telling you to re test things right now. If we had more good news to share, we would, but the best we can really tell you is that we have people actively trying to unravel this complicated thread. We’re aware that this is not the experience you expect of the game or deserve, and I promise that once we have something more meaningful to share, we’ll let you know ASAP.
In the mean time, I again thank all of you for continuing to report issues as you see them. They’re extremely invaluable when we have our QA team try to reproduce situations and help us narrow down what the common denominator might be. For those of you who do still want to report issues as you come across them, this information tends to be the most helpful in case we need to look in extra areas to make sure we have a fix.
Where were you in game when the crash happened?:
What were you doing when the crash happened?:
What error message did you get (if any)?:
What character/class you were playing when it happened?:
Was there any other notable behavior before the lockup occurred or anything you want to add?:
For the rest, we understand if you’d prefer to just lurk. As I mentioned earlier, we’ll keep you posted on this as we can, but even if we aren’t posting, we’re keeping an eye on the thread and forwarding any information of note.