[Bug 52556] New: Dragon's Lair 3D page fault when starting the game

[WineHQ Bugzilla]

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

Bug ID: 52556
           Summary: Dragon's Lair 3D page fault when starting the game
           Product: Wine
           Version: 7.2
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 71870
  --> https://bugs.winehq.org/attachment.cgi?id=71870
Highly compressed WINEDEBUG dumps and the page fault report

Dragon's Lair 3D is a 2002 game.
Interestingly, it uses OpenGL natively.

In any case, the game seems to crash on boot with a page fault:

0160:err:ole:CoUninitialize Mismatched CoUninitialize
wine: Unhandled page fault on read access to 0060A000 at address 100548ED
(thread 0134), starting debugger...

According to WineHQ reports, the last reported working version was in the Wine
1.x era.

Unfortunately, running the game with WINEDEBUG=+relay won't produce the same
error, the game silently exits in this case. I have added these dumps
regardless, they might help you. I tried figuring out which part of wine is
problematic myself, but I'm just not versed enough in the WINAPI C stuff.

I remember trying to run this throughout the wine 4.x-7.x versions, but I
always get the same error. I also remember trying some native C libraries a
while ago, but same result.

I tried compiling ancient wine versions to see where the regression happened,
but this proved too troublesome, since they require headers/packages not really
provided by modern distributions anymore.

Finally, I decided it is best to just report this bug.

My setup:

Arch Linux
Ryzen 3600X
32GB RAM
AMD RX590

In the attachment I have added these dumps:
 -WINEDEBUG=+loaddll,+relay,+seh,+tid
 -WINEDEBUG=+all
 -The wine page fault report

I can provide other dumps or try some things other things if you want as well.

An interesting observation is running this game in a 64-bit prefix will produce
a secdrv loading error. Same thing with a 32-bit WIN98 prefix. A 32-bit Windows
XP prefix does NOT produce this error, however (this is the version I used to
make these reports).