[Bug 47765] New: League of Legends occasional deadlock in client after completing game

[WineHQ Bugzilla]

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

Bug ID: 47765
           Summary: League of Legends occasional deadlock in client after
                    completing game
           Product: Wine
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 65246
  --> https://bugs.winehq.org/attachment.cgi?id=65246
Partial terminal output (intermixed wine and game output)

Occasionally, after completing a game of League of Legends and the game
exiting, the client will fail to display end-of-game content. This happens
perhaps about 5% of the time for me.

The following symptoms occur when this happens:

* The client displays a background, but no content
* Gnome repeatedly pops up a This Program is Not Responding dialog
* Sounds can still be heard from the client, at the appropriate time

I noticed the following in the terminal output when this happened:

0049:err:ntdll:RtlpWaitForCriticalSection section 0xe4cdb0 "?" wait timed out
in thread 0049, blocked by 0044, retrying (60 sec)
0044:err:ntdll:RtlpWaitForCriticalSection section 0xe4cdb0 "?" wait timed out
in thread 0044, blocked by 0009, retrying (60 sec)
0009:err:ntdll:RtlpWaitForCriticalSection section 0xe4cdb0 "?" wait timed out
in thread 0009, blocked by 0049, retrying (60 sec)

Note the three threads waiting on each other. There are other threads timing
out in RtlpWaitForCriticalSection as well, not included in this log.

Waiting does not seem to fix this. However, as a workaround, switching to a
different virtual terminal CAN apparently unstick the deadlock.

Reporting on gentoo wine-staging 4.15. This is not a new problem, I have seen
it for several months at least (possibly longer).

[Bug 47765] League of Legends occasional deadlock in client after completing game

[WineHQ Bugzilla]

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

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
          Component|ntdll                       |-unknown

--- Comment #1 from Fabian Maurer  ---
Probably not ntdll that's at fault here, it's just that the error manifests
there.
Without a way to properly reproduce it's probably hard to test for. Just 5% is
very bad.

[Bug 47765] League of Legends occasional deadlock in client after completing game

[WineHQ Bugzilla]

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

Olivier F. R. Dierick  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
         Resolution|---                         |ABANDONED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Olivier F. R. Dierick  ---
Hello,

I remember having this issue back then.

The game client was replaced and switched to 64-bit in the meantime.

Now I played several matches over the course of a few days and I didn't get any
deadlock after a match.

I think it is safe to mark this abandoned.

Regards.

[Bug 47765] League of Legends occasional deadlock in client after completing game

[WineHQ Bugzilla]

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

Gijs Vermeulen  changed:

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

--- Comment #3 from Gijs Vermeulen  ---
Closing.