http://bugs.winehq.org/show_bug.cgi?id=8770
--- Comment #68 from Baum ranger baumhaus691@onlinehome.de 2008-04-23 04:23:04 --- (In reply to comment #67)
Are you sure it is that patch? The only thing that gets changed, is a new process being addded to the end of the list of processes instead of beginning?
I'm not a developer (wished I were but I'm just not this good in coding) I have no idea if that is really the cause of everything but following the this thread for quite awhile it seams that this change helped at least a little (to get a battle.net game running). And as fare as I can tell it looks to me that this might be the cause. The changes were commited some time around the version 0.9.18, changes to the line in question seam to work for the players:
Btw, a little information: I compiled wine 0.9.45 without the change in that patch (i.e. I reverted the changes and compiled 0.9.45). It works!
So I just think there must be somebody who knows/understands why this change from v0.9.17 to 0.9.18 causes Warcraft to be 100% solid stable in single player and LAN-games (and this is really stable I can play for hours with no limitations to original windows) but totally unstable on the internet.
Battle.net is the most important thing about WarCraft and I just can't stand it any longer to boot into Windows just to play a good b.net-match (there is basicly no other reason why I have an Windows installation). I just wish somebody could fix this. And if there is nobody who can fix it I could also compile it myself (as said before) I just don't know how to find the code in question which freezes WarCraft and how it look before the crash.