[Bug 49571] New: Using the "new3D feature" of Chess base crashes the program and blocks the KDE plasma screen.

[WineHQ Bugzilla]

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

Bug ID: 49571
           Summary: Using the "new3D feature" of Chess base crashes the
                    program and blocks the KDE plasma screen.
           Product: Wine
           Version: 5.0
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: directx-d3d
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 67713
  --> https://bugs.winehq.org/attachment.cgi?id=67713
backtrace of crash Chess 11 page fault on read access to 0x00000208 in 32-bit
code (0x00604f1a)

When using:
standard install of opensuse Leap 15.2 (I confirm that it is totally borked in
15.1, so some progress).
install of chessbase 11 (Fritz 11, German version)

The program does start normally, (is actually installed on a 64 bit system,
with a copatibility of 64 bit..) you can set the screen output.
2d, old 3d and new3d. When setting 2d works, old 3d works. 
But the more recent 3d setting:
crashes with the report in attachment. 
Does block wine (so you need another session of another user to kill it via
e.g. ksysgard. Then you will find the screen filled with a frozen version of
chess 11.
Again you have to go in another user and kill the chess program as root / sudo.

The issue should be related to how the Intel graphics handle 3d, because the
very same program, same version, (all identical) runs fine in all settings with
AMD graphics.

I put this to critical because a unprepared user would be left with a machine
that would run, but he would have to hard reboot. Note that using the
combination ctrl+alt+esc does NOT kill the frozen chess 11 window. So in order
to do whatever the user must have knowledge either of alt+cntr+Fn to reach a
console or have an extra user open prior to the accident.

The program is not available for free. It has however in the 11 version a very
low cost. It is normally reported as excellent compatibility (gold).

This is probably a duplicate of bug 42055 (page fault on read access to
0x00000208 in 32-bit code (0x00604f1a).  But as I am not familiar with your
duplicate policy and since the version described is 13, it might be you wish a
separate report.