Crash on Linux

[mayansymbol]

Able to load into the main menu, but attempting to try out a hero results in the game crashing after a short loading screen. If there's a location for crash logs, I would provide them. The best I have is the following assertion:

xe: ../src-wine/dlls/ntdll/unix/virtual.c:1907: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed.

System information

Computer Information:​

Manufacturer: Gigabyte Technology Co., Ltd.
Model: B650 AORUS ELITE AX
Form Factor: Desktop
No Touch Input Detected

Processor Information:​

CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 9 7950X3D 16-Core Processor
CPU Family: 0x19
CPU Model: 0x61
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5759 MHz
32 logical processors
16 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:​

"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.8.1-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12101011
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20240304.79797

Video Card:​

Driver: NVIDIA Corporation NVIDIA GeForce RTX 3090/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 550.54.14
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 144 Hz
VendorID: 0x10de
DeviceID: 0x2204
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 2
Primary Display Resolution: 3440 x 1440
Desktop Resolution: 5360 x 1440
Primary Display Size: 31.50" x 12.99" (34.06" diag), 80.0cm x 33.0cm (86.5cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 24576 MB
Supported MSAA Modes: 2x 4x 8x 16x

Sound card:​

Audio device: Nvidia GPU 9a HDMI/DP

Memory:​

RAM: 63440 Mb

VR Hardware:​

VR Headset: None detected

Miscellaneous:​

UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 1738599 MB
Largest Free Hard Disk Block: 1218961 MB

Storage:​

Number of SSDs: 3
SSD sizes: 4000G,2000G,1000G
Number of HDDs: 0
Number of removable drives: 0

 

[intcoms]

I'm also getting this - however I've attempted to get more detailed crash logs - this seems to be the exception and surrounding logs:

385840.635:0108:011c:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
385840.635:0108:011c:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000BE0980, 10002, 0000000001A3F8A0: stub
385840.677:0108:011c:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
385840.677:0108:011c:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 0000000000C15440, 10002, 0000000001A3F8A0: stub
385840.906:0128:012c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
385841.186:0128:012c:fixme:file:NtFsControlFile FSCTL_GET_REPARSE_POINT semi-stub
385841.186:0128:012c:fixme:file:NtFsControlFile FSCTL_GET_REPARSE_POINT semi-stub
385841.186:0128:012c:trace:seh:GetModuleBaseNameA 12, L"project8.exe"
385846.542:0128:012c:fixme:file:NtFsControlFile FSCTL_GET_REPARSE_POINT semi-stub
385846.542:0128:012c:fixme:file:NtFsControlFile FSCTL_GET_REPARSE_POINT semi-stub
385846.542:0128:012c:trace:seh:GetModuleBaseNameA 12, L"project8.exe"
385846.717:0128:01b8:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005.
385846.717:0128:01b8:trace:seh:dispatch_exception code=c0000005 flags=0 addr=00006FFFFFB455BA ip=6fffffb455ba
385846.717:0128:01b8:trace:seh:dispatch_exception  info[0]=0000000000000001
385846.717:0128:01b8:trace:seh:dispatch_exception  info[1]=00007ae64ed00000
385846.717:0128:01b8:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
385846.717:0128:01b8:trace:seh:dispatch_exception  rax=0101010101010101 rbx=00000000f505d800 rcx=00007ae64ed00000 rdx=0000000000000000
385846.717:0128:01b8:trace:seh:dispatch_exception  rsi=0000000000000002 rdi=0000000089b1f2a8 rbp=0000000089b1f0a0 rsp=0000000089b1f018
385846.717:0128:01b8:trace:seh:dispatch_exception   r8=0000000000010000  r9=00007ae64ed00000 r10=0000000000010000 r11=00000000007c1800
385846.717:0128:01b8:trace:seh:dispatch_exception  r12=0000000089b1f350 r13=0000000089b1f1b0 r14=0000000000000001 r15=0000000089b1f358
385846.717:0128:01b8:trace:seh:call_vectored_handlers calling handler at 00006FFFFCEEC770 code=c0000005 flags=0
385846.717:0128:01b8:trace:seh:call_vectored_handlers handler at 00006FFFFCEEC770 returned 0
385846.717:0128:01b8:trace:seh:call_vectored_handlers calling handler at 00006FFFFD4BB3E0 code=c0000005 flags=0
385846.717:0128:01b8:trace:seh:call_vectored_handlers handler at 00006FFFFD4BB3E0 returned 0
385846.717:0128:01b8:trace:seh:call_vectored_handlers calling handler at 00006FFFFD23C050 code=c0000005 flags=0
385846.717:0128:01b8:trace:seh:call_vectored_handlers handler at 00006FFFFD23C050 returned 0
385846.717:0128:01b8:trace:seh:call_vectored_handlers calling handler at 0000000180137030 code=c0000005 flags=0
385846.717:0128:01b8:trace:seh:call_vectored_handlers handler at 0000000180137030 returned 0
385846.717:0128:01b8:warn:seh:virtual_unwind backtrace: 00006FFFFFB455BA: L"msvcrt.dll" + 00000000000455BA.
385846.717:0128:01b8:trace:unwind:RtlVirtualUnwind type 1 rip 6fffffb455ba rsp 89b1f018
385846.717:0128:01b8:trace:unwind:dump_unwind_info **** func 455a0-4567b

 

[intcoms]

adding -vulkan seems to fix this specific error.

 

[ozoned]

I just joined and I'm also getting this error. I attempted to add the -vulkan flag, but still experiencing crashes in the same spot. I'm on Debian 12. I did find an old GitHub incident about Endzone that suggested disabling FSync and ESync, but this doesn't seem to have an affect on Deadlock as even with

PROTON_NO_FSYNC=1 %command%

I still see:

fsync: up and running.

In the output and I crash when loading in after picking a character.

 

[ataberkozen123]

Try this before running your game:
sudo sysctl -w vm.max_map_count=2147483642

If this resolves your issues, you can make it permanent by creating and pasting "vm.max_map_count = 2147483642" inside /etc/sysctl.d/80-mmapcount.conf without quotes.

 

[ozoned]

Upping the vm.max_map_count to 2147483642 worked for me. Thank you @ataberkozen123

 

[Schneider(9er)Zero]

Try this before running your game:
sudo sysctl -w vm.max_map_count=2147483642

If this resolves your issues, you can make it permanent by creating and pasting "vm.max_map_count = 2147483642" inside /etc/sysctl.d/80-mmapcount.conf without quotes.

Is there any explanation as to what exactly this is and how the answer was derived? This fixed my game as well... running linux mint on kernel 6.8.0-39

 

[ozoned]

I can tell you what it does, as for how someone figured it out or why it happens, that I don't know.

vm.max_map_count allows for the application to request additional segments of memory. Once it hits the value and still needs to request more, well you don't get anymore so you essentially run out of memory while the system still have plenty of available memory. You're just using up the max maps of memory you can use. If you know file inodes vs storage space, that's how I imagine it is, though not totally sure.

How someone figured it out, that I can't say. When I was attempting to check for error messages I don't remember seeing any OOM messages.

 

[Schneider(9er)Zero]

I can tell you what it does, as for how someone figured it out or why it happens, that I don't know.

vm.max_map_count allows for the application to request additional segments of memory. Once it hits the value and still needs to request more, well you don't get anymore so you essentially run out of memory while the system still have plenty of available memory. You're just using up the max maps of memory you can use. If you know file inodes vs storage space, that's how I imagine it is, though not totally sure.

How someone figured it out, that I can't say. When I was attempting to check for error messages I don't remember seeing any OOM messages.

Well, thank you for the explanation!

 

[dosmike]

Was crashing as well, the suggested command helped, but it's not ideal to have to jump into a terminal to be able to play the game imo...
In any case, maybe a value too small could be auto detected and reported to the player on start up, so they know what's going on

 

[ataberkozen123]

Was crashing as well, the suggested command helped, but it's not ideal to have to jump into a terminal to be able to play the game imo...
In any case, maybe a value too small could be auto detected and reported to the player on start up, so they know what's going on

See the second sentence of my reply. There's a way to make it permanent.

 

[dosmike]

See the second sentence of my reply. There's a way to make it permanent.

That's not what i meant - i mean the fact that you have to tinker at all.
Getting a crash with no visible explanation just to stumble upon a thread and then poking around the system is just not a great experience.
A popup that says "Hey, please do this or you might crash" would be nice.
(iirc newer distro versions already have the value increased by default, so there's that at least, but it was 65530 for me)

 

[ataberkozen123]

That's not what i meant - i mean the fact that you have to tinker at all.
Getting a crash with no visible explanation just to stumble upon a thread and then poking around the system is just not a great experience.
A popup that says "Hey, please do this or you might crash" would be nice.
(iirc newer distro versions already have the value increased by default, so there's that at least, but it was 65530 for me)

You're right, but we're playing using Proton and it's not going to be a supported way to play this game on Linux as Deadlock is going to be a linux native game.

 

[ben.lubar]

Try this before running your game:
sudo sysctl -w vm.max_map_count=2147483642

If this resolves your issues, you can make it permanent by creating and pasting "vm.max_map_count = 2147483642" inside /etc/sysctl.d/80-mmapcount.conf without quotes.

On my laptop, this has caused it to not crash, but it has been on the loading screen for watching this match I picked arbitrarily for several minutes now.

Edit: it loaded

Spoiler: system details

Computer Information:
Manufacturer: Dell Inc.
Model: 0M7M65
Form Factor: Laptop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: 13th Gen Intel(R) Core(TM) i7-1360P
CPU Family: 0x6
CPU Model: 0xba
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5000 MHz
16 logical processors
12 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux trixie/sid (64 bit)
Kernel Name: Linux
Kernel Version: 6.9.10-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12401000
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20240610.91380
Video Card:
Driver: Intel Mesa Intel(R) Graphics (RPL-P)
Driver Version: 4.6 (Compatibility Profile) Mesa 24.1.3-2
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 89 Hz
VendorID: 0x8086
DeviceID: 0xa7a0
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1600
Desktop Resolution: 2560 x 1600
Primary Display Size: 11.81" x 7.48" (13.98" diag), 30.0cm x 19.0cm (35.5cm diag)
Primary VRAM Not Detected
Sound card:
Audio device: %1$s
Memory:
RAM: 15683 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 958367 MB
Largest Free Hard Disk Block: 679701 MB
Storage:
Number of SSDs: 1
SSD sizes: 1024G
Number of HDDs: 0
Number of removable drives: 0

 

[Schneider(9er)Zero]

That's not what i meant - i mean the fact that you have to tinker at all.
Getting a crash with no visible explanation just to stumble upon a thread and then poking around the system is just not a great experience.
A popup that says "Hey, please do this or you might crash" would be nice.
(iirc newer distro versions already have the value increased by default, so there's that at least, but it was 65530 for me)

Out of curiosity, which distros have that value increased?

But, Oh come on now... we should definitely push for it to be better but having to submit a single command into a file to make it permanent isn't really a huge deal. With all due respect, lets not pretend that we don't have to 'google' things even for Windows games on many occasions..

 

[Schneider(9er)Zero]

You're right, but we're playing using Proton and it's not going to be a supported way to play this game on Linux as Deadlock is going to be a linux native game.

Is it not already running on linux natively? I don't have proton enabled for the game in my steam library and this command still fixed the problem.

 

[Lyncola]

I'll have to get this game running on Debian 13 Testing and see how this game performs. Thanks for the command, i'll try that as well. Excited for a native linux port (if it's not already a native port)

 

[while_true_crash]

Try this before running your game:
sudo sysctl -w vm.max_map_count=2147483642

If this resolves your issues, you can make it permanent by creating and pasting "vm.max_map_count = 2147483642" inside /etc/sysctl.d/80-mmapcount.conf without quotes.

This does indeed work, thank you.
IIRC it was required for Hogwards Legacy as well on launch.