[Bug 41054] New: Battle.net.exe deadlocks in CriticalSection

https://bugs.winehq.org/show_bug.cgi?id=41054

Bug ID: 41054
           Summary: Battle.net.exe deadlocks in CriticalSection
           Product: Wine-staging
           Version: 1.9.15
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]
      Distribution: ---

Trying to launch Blizzard's Battle.net.exe using Wine Staging 1.9.15 RPMs from
Fedora 24. However, the process deadlocks and prints messages like:

err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in
thread 0063, blocked by 0000, retrying (60 sec)

This happens with both 32 bit and 64 bit prefixes. Disabling all "staging"
options via winecfg does not help.

[Bug 41054] Battle.net.exe deadlocks in CriticalSection

https://bugs.winehq.org/show_bug.cgi?id=41054

--- Comment #1 from Chris Rankin  ---
Fedora 24's previous Wine Staging RPMs were 1.9.12, and these did not cause
Battle.net to deadlock.

[Bug 41054] Battle.net.exe deadlocks in CriticalSection

https://bugs.winehq.org/show_bug.cgi?id=41054

Timur Kristóf  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 41054] Battle.net.exe deadlocks in CriticalSection

https://bugs.winehq.org/show_bug.cgi?id=41054

--- Comment #2 from Timur Kristóf  ---
Some observations:
- This bug seems to only affect the Battle.net client, Starcraft II can still
launch fine (if the executable is launched directly)
- Downgrading to 1.9.9 or 1.9.12 makes the problem go away
- Many users on the internet who experience this problem say that switching
from wine-staging to regular wine also makes the issue go away

[Bug 41054] Battle.net.exe deadlocks in CriticalSection

https://bugs.winehq.org/show_bug.cgi?id=41054

Sebastian Lackner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Sebastian Lackner  ---
Not major (see bug reporting guidelines).

Thanks for the report, this issue was fixed by:
https://github.com/wine-compholio/wine-staging/commit/69b39e2f8a5804c5d40c44...

The fixed patch will be included with the next release. Sorry for the
inconvenience.

[Bug 41054] Battle.net.exe deadlocks in CriticalSection because of wrong DLL load order

https://bugs.winehq.org/show_bug.cgi?id=41054

Sebastian Lackner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Battle.net.exe deadlocks in |Battle.net.exe deadlocks in
                   |CriticalSection             |CriticalSection because of
                   |                            |wrong DLL load order

[Bug 41054] Battle.net.exe deadlocks in CriticalSection because of wrong DLL load order

https://bugs.winehq.org/show_bug.cgi?id=41054

--- Comment #4 from Timur Kristóf  ---
The issue no longer appears, as of wine-1.9.16-1.fc24.x86_64

[Bug 41054] Battle.net.exe deadlocks in CriticalSection because of wrong DLL load order

https://bugs.winehq.org/show_bug.cgi?id=41054

Sebastian Lackner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |draekko.software+wine@gmail
                   |                            |.com

--- Comment #5 from Sebastian Lackner  ---
*** Bug 41076 has been marked as a duplicate of this bug. ***

[Bug 41054] Multiple applications fail to start when MSVCP140 is set to native ( Battle.Net, Photoshop CC 2015.5)

https://bugs.winehq.org/show_bug.cgi?id=41054

Sebastian Lackner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Battle.net.exe deadlocks in |Multiple applications fail
                   |CriticalSection because of  |to start when MSVCP140 is
                   |wrong DLL load order        |set to native (Battle.Net,
                   |                            |Photoshop CC 2015.5)

[Bug 41054] Multiple applications fail to start when MSVCP140 is set to native ( Battle.Net, Photoshop CC 2015.5)

https://bugs.winehq.org/show_bug.cgi?id=41054

tokktokk  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 41054] Multiple applications fail to start when MSVCP140 is set to native ( Battle.Net, Photoshop CC 2015.5)

https://bugs.winehq.org/show_bug.cgi?id=41054

Alistair Leslie-Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #6 from Alistair Leslie-Hughes  ---
Closing Fixed Staging 3.14