[Bug 58216] New: Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

Bug ID: 58216
           Summary: Inquisitor crashes on start
           Product: Wine
           Version: 10.7
          Hardware: x86-64
               URL: https://store.steampowered.com/app/241620/Inquisitor/
                OS: Linux
            Status: NEW
          Keywords: regression
          Severity: normal
          Priority: P2
         Component: winegstreamer
          Assignee: [e-mail]
          Reporter: [e-mail]
   Regression SHA1: 075033d61ffac2a8d42e06e91a12c88f2fa17401
      Distribution: ArchLinux

Created attachment 78529
  --> http://bugs.winehq.org/attachment.cgi?id=78529
terminal output

The intro video in Inquisitor never worked for me: it was gracefully skipped
and the game loaded directly the main menu.

Since Wine-10.7 the game crashes right after start.

Reverting the following commit fixes the crash for me:
commit 075033d61ffac2a8d42e06e91a12c88f2fa17401
winegstreamer: Make sure WMSyncReader never reads in the background.

'winetricks wmp9' also makes the crash go away (the startup video still does
not work).

Reproduced with the Steam and GOG.com versions.

wine-10.7-73-gf9741837a3b

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

[e-mail] changed:

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

--- Comment #1 from [e-mail] ---
Hi, I tested steam version of Inquisitor with wine 10.7 vanilla and staging,
and can't seem to reproduce the problem described.

Can you reproduce the crash with WINEDEBUG=seh,unwind,module,wmvcore, and
attach the log?

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #2 from Béla Gyebrószki  ---
Created attachment 78741
  --> http://bugs.winehq.org/attachment.cgi?id=78741
WINEDEBUG=seh,unwind,module,wmvcore log

(In reply to yshuiv7 from comment #1)
> Hi, I tested steam version of Inquisitor with wine 10.7 vanilla and staging,
> and can't seem to reproduce the problem described.
>
> Can you reproduce the crash with WINEDEBUG=seh,unwind,module,wmvcore, and
> attach the log?

Hello and thank you for triaging this bug report.
Did you try the game with the "new" WOW64-style Wine?
I still haven't switched to it, but I tried it now: the game doesn't crash with
the new WOW64 Wine, but the crash is still present using a pure 32-bit or the
"old" WOW64 Wine.
Which makes me think there is something fishy with my 32-bit GStreamer-plugins
installation (?)
Could you check my debug log to see if anything comes up (created with a 32-bit
Wine).

wine-10.9-192-g37abd61d126

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #3 from [e-mail] ---
oh, you are absolutely right, and i was testing with new wow64. and yes, i can
reproduce this on old wow.

btw, do you also see a "pure virtual function call" message box before the game
crashes? interestingly i see the same thing on proton.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #4 from Béla Gyebrószki  ---
(In reply to yshuiv7 from comment #3)
> btw, do you also see a "pure virtual function call" message box before the
> game crashes? interestingly i see the same thing on proton.

Yes, there is such a message box just before the Wine crash reporter would kick
in.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #5 from [e-mail] ---
Hi, I just tried this on wine 10.15, old WoW64 build, and the game seems to be
working now.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #6 from Béla Gyebrószki  ---
(In reply to yshuiv7 from comment #5)
> Hi, I just tried this on wine 10.15, old WoW64 build, and the game seems to
> be working now.

Can't confirm this. Still the same error when starting the game in Wine-10.15
using the old wow64 method or a 32-bit wine build.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #7 from [e-mail] ---
There is a recent use-after-free fix in winegstreamer that has gotten into
10.15 so I thought that might be it :(

And this is really weird. I am tried old-WoW and 32-bit, both works. The video
still does play but I can even hear its audio playing. After that, the game
starts. I wonder what's different between your setup and mine.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #8 from [e-mail] ---
> The video still does play [...]

Typo. I meant "still does _not_ play".

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

Stian Low  changed:

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

--- Comment #9 from Stian Low  ---
(In reply to Béla Gyebrószki from comment #0)
> Since Wine-10.7 the game crashes right after start.

Confirming bugs for WINE 10.15 commit 0abb419016e for shared WoW64 for GOG
version. (Debian 13)

New WoW64 works as expected.

Even GOG installer is broken for shared WoW64 which throws popup error "Invalid
Handle"

The same popup error "Invalid Handle" is thrown when launching the game after
installing via new WoW64 but with an additional popup error after clicking OK:
"There is no Windows program configured to open this type of file"

Logs without any WINEDEBUGs:
0150:err:environ:init_peb starting
L"Z:\home\any\Downloads\game-inquisitor\install\Inquisitor\GameData\Inquisitor.exe"
in experimental wow64 mode
wine: failed to load L"\??\C:\windows\syswow64\ntdll.dll" error c0000135

New WoW64 seems to be progressing well and but shared WoW64 is still used by a
lot of dependent game-oriented forks like Proton so this bug may break those
downstream projects.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #10 from Stian Low  ---
(In reply to Stian Low from comment #9)
> Logs without any WINEDEBUGs:
> 0150:err:environ:init_peb starting
> L"Z:\home\any\Downloads\game-
> inquisitor\install\Inquisitor\GameData\Inquisitor.exe" in experimental
> wow64 mode
> wine: failed to load L"\??\C:\windows\syswow64\ntdll.dll" error c0000135

Disregard for now.

C:\windows\syswow64\ntdll.dll is missing due to a bad shared wow64 install
on my part.  Fixing and retesting.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #11 from Stian Low  ---
Created attachment 79324
  --> http://bugs.winehq.org/attachment.cgi?id=79324
Backtrace with stack

(In reply to Stian Low from comment #9)
> Even GOG installer is broken for shared WoW64 which throws popup error
> "Invalid Handle"
> wine: failed to load L"\??\C:\windows\syswow64\ntdll.dll" error c0000135

(In reply to Stian Low from comment #10)
> Disregard for now.
>
> C:\windows\syswow64\ntdll.dll is missing due to a bad shared wow64
> install on my part.  Fixing and retesting.

Indeed the "Invalid Error" popups are resolved by correcting my faulty shared
WoW64 install.

Bug is now reproducible with corrected shared WoW64 install.

Attached is a backtrace with a stack which was not available for Béla's first
backtrace posted.

Backtrace also indicates unimplemented function missing by first backtrace.

Unhandled exception: unimplemented function
winegstreamer.dll.winegstreamer_create_wm_sync_reader called in wow64 32-bit
code (0x7b5f8fe8).

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #12 from Stian Low  ---
(In reply to Stian Low from comment #11)
> Unhandled exception: unimplemented function
> winegstreamer.dll.winegstreamer_create_wm_sync_reader called in wow64 32-bit
> code (0x7b5f8fe8).

Disregard again for now.

This backtrace may be a red herring for my particular shared wow64 build
because I skipped 32 bit winegstreamer because it's one of the few Debian apt
packages that causes the 64 bit versions to be uninstalled.

Previously I uninstalling 64-bit gstreamer for building 32-bit shared WINE and
reinstalling 64-bit gstreamer for building 64-bit shared WINE.

This highlights the convenience that new WoW64 provides but as stated before
share WoW64 is still being used by many downstream projects which may still
need to be supported until they migrate to new WoW64.

I'll fulfilling the 32-bit gstreamer parts missing for my shared WoW64 and
retest.

[Bug 58216] Inquisitor crashes on start

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58216

--- Comment #13 from Stian Low  ---
(In reply to Stian Low from comment #12)
> I'll fulfilling the 32-bit gstreamer parts missing for my shared WoW64 and
> retest.

Unable to reproduce crash for after fulfilling 32-bit gstreamer dependencies
via Debian apt packages while building 32-bit shared WoW64.

Inquisitor launches for shared WoW64 and seems to behave consistent with
working new WoW64.

Perhaps 32-bit gstreamer discrepancies exist with your builds similar to the
errors I encountered earlier?

Debian 13 steps that fixed prior shared WoW64 errors:

1.  Configure 64-bit shared WoW64 after installing 64-bit gstreamer dependency:
sudo apt install libgstreamer-plugins-base1.0-dev

2.  Build 64-bit shared WoW64 via `make`

3.  Configure 32-bit shared WoW64 after installing 32-bit gstreamer dependency:
sudo apt install libgstreamer-plugins-base1.0-dev:i386

4.  Build 32-bit shared WoW64 via `make`

5.  Install 32-bit shared WoW64 via `make install`

6.  Install 64-bit shared WoW64 via `make install`