Full system crash after bug report CONFIRMED

#1 - April 28, 2013, 10:26 a.m.
Blizzard Post

I have now duplicated this issue. It occurs on both pc and Mac clients. It is however, more severe on the Mac client, for me anyway. I have only observed this in the last week or so, never had it happen before on either system, but 3 times in the last week. I have filed an in-game report for 2 of 3 occurrences. (post-recovery)

On both, if I fill out a bug report, then use esc to close each panel of the ui open (confirm bug report, esc to close bug report panel, esc to close hero panel or inventory, or any other open windows), if you logout of the character immediately after that and return to the character select screen, then immediately double-click to log on to another character, the crash occurs. If I wait several minutes, I have not had a crash.

On pc, I had it prompt me to send a crash report to Anet with any description I could offer, then closed the client. I was able to recover and launch the client again.

On Mac, it is a full system lock. Initially, the graphics freeze (character idle movement stops) and the music plays smoothly until it ends, then stops. The mouse continues to work, but nothing responds. You cannot close using the X, you cannot open any options panels, but worse yet, you cannot get out of this state. Option+command+esc does absolutely nothing (no emergency force quit), you cannot tab out, trackpad swipes don’t work, and pressing the power button to get the shutdown/sleep/restart dialogue box doesn’t work either. The thing I noticed also, is the system itself acts as if the game has shut down meaning it immediately starts cooling off and the fans spin down, demonstrating that the game is not using CPU/gpu resources, it just Crashes the system. The only way to recover is to power down holding the power button until it shuts off. Then restart it.

my specs are (for Mac) just in case:

MacBook pro 15inch, late 2011
2.2ghz intel core i7
8gb ram
Amd radeon hd 6750m 512mb
OsX lion 10.7.5 (all updates complete)

Please don’t refer me to the Mac forum as they are not supported any longer (still awaiting confirmation). And considering this is a pc and Mac issue, I see no problems posting this here. Besides, no one is reading the Mac forums, so it would never be seen there by Anet (over 4 months since official post, over 2 months since a community coordinator closed a single thread).

Just wanted to leave the details where others could see and hopefully prevent an issue for them. And maybe get a fix one day.

Thanks for reading this.

#13 - May 2, 2013, 1:47 p.m.
Blizzard Post

Hi there Kyllaa – Sorry it’s taken me so long to reply to your thread. I was able to reproduce a crash on my own system following the steps that you outlined. While I didn’t experience a full system crash I did experience a client crash and so we’re going to be investigating this issue a little further. I appreciate you bringing this issue to our attention and in such detail!

#16 - June 25, 2013, 1:33 p.m.
Blizzard Post

Hey there Kyllaa – Just checking in. Are you still experiencing this issue?