Linux Crashing while passing Steam Launch Arguments

[Kackspn]

Version

2.0

Platform

Linux

I would like to have mangohud display showing while using the vulkan renderer, however, the game starts but always crashes a few seconds later
Launch args that work are "gamemoderun %command%" but prepending "mangohud" or "MANGOHUD=1" causes the game to crash
I have tried with steam overlay enabled and disabled. I was able to use mangohud just fine before the 2.0 update
Here is the log file

terminate called after throwing an instance of 'std::out_of_range'

  what():  basic_string::substr: __pos (which is 10) > this->size() (which is 9)

Caught fatal signal - signo:6 code:-6 errno:0 addr:0x3e800006145

Obtained 14 stack frames.

#0  0x00778a8064def0 in __sigaction

#1  0x00778a806a774c in pthread_key_delete

#2  0x00778a8064ddc0 in gsignal

#3  0x00778a8063557a in abort

#4  0x007789ac626b6e in (Unknown)

#5  0x007789ac76f8ba in overlay_GetInstanceProcAddr

#6  0x007789ac626a8e in (Unknown)

#7  0x007789ac76fa66 in overlay_GetInstanceProcAddr

#8  0x007789ac628725 in (Unknown)

#9  0x007789ac61a30f in (Unknown)

#10 0x007789ac6ba85a in overlay_GetInstanceProcAddr

#11 0x007789ac7faf24 in overlay_GetInstanceProcAddr

#12 0x00778a806a57eb in pthread_condattr_setpshared

#13 0x00778a8072918c in __clone

 

[WretchedDollie]

Hello Kackspn,

Based on the information provided, this does not appear to be a bug within the game itself. The crash seems to occur when launching the game with the additional Steam launch arguments related to a third-party overlay/tool. Modifying launch parameters or injecting external applications can introduce instability outside the game's supported configuration.

To help isolate the issue, please try launching the game without any third-party tools or custom launch parameters. If the crash persists under a clean, default launch, please provide updated logs and system details so we can investigate further.

Best Regards,
Dollie

 

[WretchedDollie]

Hi there!

As there hasn’t been any recent activity on this report, we’ll go ahead and wrap it up for now.
If the issue appears again in the current stable build, please open a new report and include the output log along with any extra details that might help us dig deeper.

Thank you!
Dollie