[Bug 49931] New: 64-bit Dota 2 randomly crashes, but 32-bit Dota 2 works perfectly

[WineHQ Bugzilla]

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

Bug ID: 49931
           Summary: 64-bit Dota 2 randomly crashes, but 32-bit Dota 2
                    works perfectly
           Product: Wine
           Version: 5.18
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

To reproduce:

1. Install Steam for Windows.

2. Install Dota 2 via `wine 'C:\Program Files (x86)\Steam\steam.exe'
steam://run/570`. This will install both the 32-bit and the 64-bit version of
the game.

3. Start 64-bit Dota via `wine 'C:\Program Files
(x86)\Steam\steamapps\common\dota 2 beta\game\bin\win64\dota2.exe'`.

4. In the lower-right corner, click Play Dota, Practice With Bots, Solo, Start
Bot Match.

5. Click on any hero, click Lock In, and wait for the game to start.

Before the game starts, Dota freezes, then crashes. Sometimes it crashes before
you even click Play Dota. Sometimes it crashes right after the map starts
rendering.

No useful information is written to the console in vanilla Wine. However, in
Wine Staging, lines similar to the following are printed repeatedly right
before the crash:

04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range
0x7f1522b50000-0x7f1522b53000, unix_prot 0x7.
04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range
0x7f1522c80000-0x7f1522c83000, unix_prot 0x7.
04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range
0x7f1523ad0000-0x7f1523ad3000, unix_prot 0x7.
04b8:err:virtual:alloc_area_in_reserved_or_between_callback Could not map in
reserved area.
m Files (x86)\Steam\steamapps\common\dota 2 beta\game\bin\win64\dota2.exe:
../wine-staging/dlls/ntdll/unix/virtual.c:1286: create_view: Assertion
`!((UINT_PTR)base & page_mask)' failed.

If you instead run 32-bit Dota via `wine 'C:\Program Files
(x86)\Steam\steamapps\common\dota 2 beta\game\bin\win32\dota2.exe'`, the game
runs perfectly.

[Bug 49931] 64-bit Dota 2 randomly crashes, but 32-bit Dota 2 works perfectly

[WineHQ Bugzilla]

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

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.winehq.org/sho
                   |                            |w_bug.cgi?id=46568
                 CC|                            |[e-mail]
                URL|                            |https://cdn.cloudflare.stea
                   |                            |mstatic.com/client/installe
                   |                            |r/SteamSetup.exe
           Keywords|                            |download

--- Comment #1 from Alex Henrie  ---
Pinging Paul Gofman, the author of the Wine Staging patch that prints the error
messages.

[Bug 49931] 64-bit Dota 2 randomly crashes, but 32-bit Dota 2 works perfectly

[WineHQ Bugzilla]

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

[e-mail] changed:

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

--- Comment #2 from [e-mail] ---
Created attachment 70601
  --> https://bugs.winehq.org/attachment.cgi?id=70601
terminal output of 64-bit version crash

present in 6.16

the game now crashes consistently before the valve logo appears while it's
loading (this change seems to be from a game update instead of a wine update,
since I tested a few times with 5.18)

it is apparently crashing due to an exception, that gets captured automatically
which might be counterproductive since the backtrace in the minidump doesn't
seem useful (the crash handler might be unwinding the stack before writing the
minidump?)

there still seems to be some inconsistency in how much the loading animation
runs before the game crashes, which along with the previous behaviour might
point to some sort of race condition which is either causing the crash or is
obscuring the problem

an additional note is that I'm running it with the -vulkan option, the d3d11
backend crashes in the same way but has some additional d3d11 fixmes in the
output