Diablo® III

Leave Game Button Exits D3 Completely Instead

See this thread for details:
http://us.battle.net/en/forum/topic/9972107447

Looks like I have a way to reproduce it consistently:
1. Resume the current quest (doesn't seem to matter what it is).
2. While in the quest/game, switch to Finder (i.e. with Command-Tab)
3. Switch back to D3
4. Click the button to bring up the menu
5. Click on Leave Game
6. Exits D3 instead of just the game.

Mac OSX 10.7.4
Also running Battle.Net desktop beta.
Reply Quote
90 Orc Warlock
8040
I'm experiencing this bug as well. It's worse when you don't run the game full screen as the likelihood of switching to another app is much more likely.
Reply Quote
MVP - Technical Support
View profile
I have attempted to reproduce this error several times and have been unsuccessful in doing so. When you are starting Diablo 3 via the BDA, are you quitting BDA at any time after D3 has launched?

Leave Game functions just fine here. Exit Game drops me back to the Finder, but then again, it does so only because I actively quit the BDA the moment I click Play so it isn't in the background taking resources. In this case, the game is working properly as without the BDA open, it has nothing to hook into when exiting the game client.
________________________________________________
Technical Support MVP
Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
Caution: This cookie bites back.
Reply Quote
90 Orc Warlock
8040
I almost always have the Battle.net app running, I never quit it. At most I would close the window.

The D3Debug.txt file contains a bunch of sendto() failed's - not sure if that's what might be causing the issue?

Here's a small snippet from the end.

2014.01.13 12:10:05.556563130 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.586267396 >>> Marbar BnetParty::LeaveGameByMyself currentGameId=game_id { factoryId: 5988331798699628454 high: 432345578499141255 low: 12505807140785713144 }
2014.01.13 12:10:05.586453662 >>> Marbar SendGameServerMessage_StartLeaveGameCountdown eContext=0
2014.01.13 12:10:05.586603304 >>> Marbar BnetParty::LockPartyForReason LEAVING_CURRENT_GAME(3)
2014.01.13 12:10:05.586729318 >>> Marbar BnetParty::CloseStatusChange_SetJoinPermission newPartyJoinPermission=CLOSED(1) reason=LEAVING_CURRENT_GAME(3)
2014.01.13 12:10:05.586906224 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.606683231 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.622617096 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.640638568 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.669632460 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.669805995 >>> Marbar BnetPartyState::SetJoinPermission CLOSED(1) SetPrivacyLevel token=341 callback_code= (10016)
2014.01.13 12:10:05.669922087 >>> Marbar BnetParty::CloseStatusChange_SetPrivacyLevelCallback code=0 old=CLOSED_GAME_PAUSED(2) new=CLOSED(1) reason=LEAVING_CURRENT_GAME(3)
2014.01.13 12:10:05.670183292 >>> Marbar Party::NotifyLeaveGameCountdownEvent newState=STARTED countSubscribers=2
2014.01.13 12:10:05.670695300 >>> Marbar SendGameServerMessage_FinishLeaveGame_RequestExitNow
2014.01.13 12:10:05.670794793 >>> Marbar Party::NotifyLeaveGameCountdownEvent newState=FINISHED countSubscribers=2
2014.01.13 12:10:05.688670849 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.705655708 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.735639005 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.735821834 >>> Marbar BnetParty::UnlockPartyForReason GAME_IS_PAUSED(4)
2014.01.13 12:10:05.754789666 sendto() failed: Address is not available for this machine or is an invalid address.
2014.01.13 12:10:05.754997129 >>> Marbar Quit game reason=0
2014.01.13 12:10:10.825640884 Error: gethostbyname(Barretts-MacBook-Pro.local): Unknown host
2014.01.13 12:10:10.825785086 Warning: XNetAddress::FromString returning Empty Address: Address string=Barretts-MacBook-Pro.local, defaultport = 0
2014.01.13 12:10:10.826441629 gethostbyname error: Address is not available for this machine or is an invalid address.
Reply Quote
MVP - Technical Support
View profile
I'm assuming you're on either 10.9.0 or 10.9.1, as those sandbox errors crop up by the metric crapton in Mavericks. Those are unfortunately Mavericks bugs, not D3 bugs.

I wish I could see a video of your screen showing exactly how this happens, as I cannot recreate the scenario no matter what I try.
________________________________________________
Technical Support MVP
Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
Caution: This cookie bites back.
Reply Quote
90 Orc Warlock
8040
I think I might have fixed whatever it was by doing the following:

Exit the Game (it can't be running)
In the B.net app choose Options -> Scan and Repair

Either I've just had a lucky string were it hasn't crashed or that fixed it.

Edit: Spoke too soon. It seems to have reduced the problem, but not eliminated it.
Edited by BarrettJ#1428 on 1/15/2014 12:24 PM PST
Reply Quote
MVP - Technical Support
View profile
Is there any chance you could get a screen recording via QuickTime to show the actual steps you take to reproduce this? I'm still not seeing it on my end even after nearly 50 attempts.
________________________________________________
Technical Support MVP
Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
Caution: This cookie bites back.
Reply Quote
I first reported this issue a year ago and it has never been resolved. About 50% of the time, starting a game then leaving will immediately exit to desktop without any prompt. I think this bug might have been introduced in patch 1.0.6. I'm certain this has nothing to do with the BDA or Mavericks.
Reply Quote
MVP - Technical Support
View profile
The sandbox errors are likely Mavericks related (it's filled with them as my 1 GB console log collection can attest to). The other issue is something I've not ever seen and cannot reproduce on either the Live client or the Beta/PTR client.
________________________________________________
Technical Support MVP
Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
Caution: This cookie bites back.
Reply Quote
90 Orc Warlock
8040
Doing the scan and repair seems to have made the issue much less frequent for me. I attempted to record it happening, but it didn't happen during the 30 minutes I had the patience to try to capture it (it literally crashed right before I started trying to record it, and then I probably launched and reopened the game a good 50 times while it was recording to try to capture it).

It really is as simple as launch the game, click resume, click on your wallpaper (assuming game is running window mode), click back on game, hit esc and choose leave game, game will crash instead of going to the "lobby".

I haven't played on the PTR a ton, but I also haven't seen the issue occur there, so with any luck the issue is fixed for RoS/2.0
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]