http://bugs.winehq.org/show_bug.cgi?id=18997
Summary: Warcraft 3 1.23 crashes after remaining one minute in a Battle.net chat room. Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 AssignedTo: wine-bugs@winehq.org ReportedBy: florian@fkoeberle.de
This bug report is about the crash which happens, if you remain one minute in a chat room of the Warcraft III Battle.net.
This bug report is NOT about the crash which happens at login time: Bug report 17809 is about that crash.
The application entry HOWTO explain in the section "How to get Battle.net working?" how to work around this bug: http://appdb.winehq.org/objectManager.php?sClass=version&iId=3126
Please do not ask for help in this bug report. No one wants to read tones of comments. Thanks! Logs (traces etc.) are not needed at the moment as it is known where the crash happens (see below).
This bug is a regression caused by partly implemented functionality, the commit which introduced the regression is: e00e5a37e280c7e07da551ae6a2e9d3e57d6a7b9 is first bad commit commit e00e5a37e280c7e07da551ae6a2e9d3e57d6a7b9 Author: Henri Verbeet hverbeet@gmail.com Date: Mon Oct 20 09:26:45 2008 +0200
secur32: Implement schannel InitializeSecurityContextW.
:040000 040000 529e5211a3cdb6c5361ae8c5a31d91c90ec7a3f2 b221c3ebbdec872c3bd8c159636cc334e2cd29ee M dlls
The trace http://bugs.winehq.org/attachment.cgi?id=20398 shows that DeleteSecurityContext gets called twice with the same handle. The trace does not contain the crash stackstrace as Warcraft 3 catch the exception and writes down it's own stacktrace file.
The trace has been made with a wine build based on commit 1f00a870ec6ee of my repository: http://repo.or.cz/w/wine/warcraft3.git?a=log;h=1f00a870ec6ee172afa7ffc82a169...
So the bug is either that it should be possible to delete a security context twice or the bug causes the DeleteSecurityContext method to be called twice.