http://bugs.winehq.org/show_bug.cgi?id=17809
yournameinhere yournameinhere@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yournameinhere@googlemail.co | |m
picca picca@pudr.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |picca@pudr.com
Joseph bomber joseph.bomber@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.bomber@gmail.com
Toon Geens geens.toon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |geens.toon@gmail.com
Matheus Ribeiro mfribeiro@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mfribeiro@gmail.com
Eivind to.eivind@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |to.eivind@gmail.com
Florian florian@fkoeberle.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #20103|0 |1 is obsolete| |
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
Alexander Kojevnikov alexander@kojevnikov.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander@kojevnikov.com
--- Comment #28 from Nicky nheart@gmail.com 2009-03-28 07:56:43 --- After this patch the game doesn't crash in chat (only sometimes there's a "Connection to battle.net lost" but no crash) However when you start a ladder game there's a crash while loading the game - the crash is the same Acces Violation. Custom games still work fine, though...
--- Comment #29 from picca picca@pudr.com 2009-04-02 12:35:21 --- I had these issues with W3FT 1.23 too. So I downgraded to wine 1.1.4 and so far everything looks stable. No crashes.
--- Comment #30 from Joseph bomber joseph.bomber@gmail.com 2009-04-02 13:40:27 --- I down graded to 1.1.4 after having the type B crashes and it did stop crashing. Though arranged games still dont work, once you find a game it brings up an error message (but battle net doesn't crash... which is nice).
--- Comment #31 from Charles McGarvey onefriedrice@brokenzipper.com 2009-04-05 18:53:19 --- Confirmed: 1.1.4 fixes both types of crash for me.
--- Comment #32 from Toon Geens geens.toon@gmail.com 2009-04-06 07:32:54 --- Does anyone have an 1.1.4 64bit .deb for Intrepid or Jaunty ? Or how do I fetch 1.1.4 from the gitrepository to try and compile it myself ?
--- Comment #33 from Toon Geens geens.toon@gmail.com 2009-04-06 08:07:46 --- Installed 1.1.4 .deb for Hardy in Jaunty beta and still getting the same crash.
How can I get the 1.1.4 source from the git repo to compile this myself ? There is no 1.1.4 .deb available for Intrepid of Jaunty.
--- Comment #34 from Matheus Ribeiro mfribeiro@gmail.com 2009-04-06 09:17:05 --- Compiled 1.1.4 here and bnet problem disappears. But still have the crashes while saving in single player.
--- Comment #35 from Eivind to.eivind@gmail.com 2009-04-07 14:09:02 --- Downgraded to 1.1.4 and it seams to work fine. Posted patch didn't do squat for me ( on 1.1.18 ), but can't guarantee it was correctly applied (just did a really quick ebuild (added: epatch {$FILESDIR}/1.1.18-wc3-invalid-handle.patch), and I'm not really experienced with patching ;) )
amd64 gcc (Gentoo 4.3.3-r2 p1.1, pie-10.1.5) 4.3.3 kernel 2.6.29-gentoo-r1 wine 1.1.4 and 1.1.18.
--- Comment #36 from anomalydetected@gmail.com 2009-04-08 22:30:23 --- Well I'll be darned. I too tried compiling a fresh 1.1.4 version, and the battle.net problem is not present. I don't see the banner ads at all (and don't care too), but the crash does not happen.
So to you dev types: what is a good next step toward this getting resolved in future versions? Should I do a regression test?
--- Comment #37 from Toon Geens geens.toon@gmail.com 2009-04-09 01:58:42 --- Are you all sure the battle net problem is gone with 1.1.4 ? The crash is still there between the 20th en the 30th minute of a custom game (3 out of 3 tries) for me.
Using Ubuntu Jaunty with wine 1.1.4 (.deb for Hardy :s)
--- Comment #38 from anomalydetected@gmail.com 2009-04-09 10:16:58 --- On 1.1.18, the crash for me would happen very quickly, usually within about a minute or so of being in chat. On 1.1.4, I was able to chat for quite awhile but did not time how long. You bring up a good point - maybe the issue is just improved and not completely gone - so I'll spend some more time and actually clock how long I can stay in chat, run a few long games, etc. to confirm whether or not it is completely gone. I'll report back here when done.
Also, I haven't personally verified that 1.1.4 is the latest version where the problem has (or at least seems to have) gone away. Not sure how the first person figured out that 1.1.4 was the magic version. Has anyone confirmed if it still happens almost immediately in 1.1.5 yet? If I cannot make 1.1.4 fail, I'll start going up the chain and see what the first verison that does fail is.
--- Comment #39 from Florian florian@fkoeberle.de 2009-04-10 06:30:35 --- 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
--- Comment #40 from Florian florian@fkoeberle.de 2009-04-10 06:41:29 --- Created an attachment (id=20360) --> (http://bugs.winehq.org/attachment.cgi?id=20360) secur32: Disable schannel InitializeSecurityContextW.
The implementation of schannel is incomplete. This patch makes InitializeSecurityContextW a stub again, to prevent Warcraft 3 from crashing when the user is one minute in a battle.net chat room.
I updated the git repository (website: http://repo.or.cz/w/wine/warcraft3.git) with the warcraft 3 patches.
If you have checked it out you can update to the newest patches by executing the following commands in the checkout out directory: git fetch -f git rebase origin make
If you haven't checked it out so far then following my instructions from comment #27 is enough.
--- Comment #41 from Florian florian@fkoeberle.de 2009-04-12 08:38:34 --- Created an attachment (id=20398) --> (http://bugs.winehq.org/attachment.cgi?id=20398) trace+secur32 until crash with slightly modified wine-1.1.19
The attached trace 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...
--- Comment #42 from Florian florian@fkoeberle.de 2009-04-12 08:51:57 --- The trace contains some "magical numbers", here are the symbols:
The argument fContextReq=49436 of the InitializeSecurityContextW calls is 0xc11c in hex and has the following meaning: #define ISC_REQ_STREAM 0x00008000 #define ISC_REQ_EXTENDED_ERROR 0x00004000 #define ISC_REQ_ALLOCATE_MEMORY 0x00000100 #define ISC_REQ_CONFIDENTIALITY 0x00000010 #define ISC_REQ_SEQUENCE_DETECT 0x00000008 #define ISC_REQ_REPLAY_DETECT 0x00000004
The attribute 83 (0x53) of the QueryContextAttributesA call has the following meaning: #define SECPKG_ATTR_REMOTE_CERT_CONTEXT 0x53