http://bugs.winehq.org/show_bug.cgi?id=30849
voltara@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |voltara@gmail.com
--- Comment #4 from voltara@gmail.com 2012-06-05 15:13:07 CDT --- Based on examining a tcpdump of the battle.net connections:
Diablo3 opens a connection when you log in. I'll call this the "account" connection. When the "account" connection is idle, the server sends keepalive messages every 20 seconds, and the client responds immediately to each keepalive.
Upon joining a game, Diablo3 opens a second connection. I'll call this the "game" connection, where the game-related communication happens. The "account" connection is kept open as well. Immediately upon joining the game, Diablo3 (under wine) stops responding to the server's keepalive packets. Leaving the game does not remedy this.
After 150 seconds of failing to respond to the keepalive, the server closes the "account" connection, and also closes the "game" connection (if one exists.) If in a game, the message is "You have been removed from the game." If not in a game, no message is displayed.
After its "account" connection is closed, the Diablo3 game client becomes unresponsive to commands. Attempting to exit the game hangs it. If I was to make a guess, I think it's trying to send a "log out" message over the (already closed) "account" connection, and hanging while waiting for a response.