[Bug 45369] New: Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed

[wine-bugs at winehq.org]

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

            Bug ID: 45369
           Summary: Under certain (unknown) conditions, winedbg.exe
                    continually spawns explorer.exe sub-processes until it
                    is killed
           Product: Wine-staging
           Version: 3.10
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: roman at hargrave.info
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

Created attachment 61679
  --> https://bugs.winehq.org/attachment.cgi?id=61679
A portion of wine console output collected after the event

I'd like to open with a note that I am not submitting this on wine-devel, as I
the only application that has been able to cause these crashes will not run
well enough to reliably reproduce the error without DXVK, and in turn
wine-staging (as far as I am aware, DXVK continues to require a patch in the
staging patchset that has not been mainlined - correct me if i am wrong).

The application which has been causing problems is Grand Theft Auto V, though
specifically Rock Star Social Club (I can't be terribly certain - but the issue
tends to crop up when social club is brought in to the question).

Glancing at the crash info in the terminal (winedbg is actually not even
visible yet as it is too preoccupied with explorer), this is the result of an
exception thrown within libcef.dll, which judging by the name and the platform
which it is used by, is chromium embedded framework - a common offender.

Knowing this, i'll just avoid the social club in-game if at all possible, but
what's concerning is the outcome. Something about the manner in which it has
gone about crashing causes some _very_ eratic behaviour in winedbg. For some
reason, `explorer.exe /desktop` is invoked as a child process of winedbg and
then fails to start. Another instance of explorer with the same parameters is
then started by the child, as well as some concurrent instances (I think - when
you have so many process running that your PIDs roll over it start to get hard
to track who started who) - effectively an explorer fork bomb, though it dies
off fast enough if you get to winedbg and kill it or its parent.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.