Crashing randomly

[哈哈哈哈]

The game crashes at random times, once shortly after I started the game and a few times while opening a door and then another time after getting past that door without issue.

I've put in a refund request as I really CANNOT see rhyme or reason for the crashing (and with no snippyness to the developer) I'm tired of buying games and them not working, however if there is any logical reason for this (Steam overlay?) I'd be happy to give it another go.

I'm running Manjaro, with i3wm (although XFCE crashes too).

[哈哈哈哈]

Turning off Steam UI and disconnecting my 360 controller hasn't / didn't help.

[哈哈哈哈]

https://youtu.be/IES3CELJm9Y

A video of the game crashing.

[张禅nnnn]

Try running the game and then go to your desktop. Once you're there, open the Task Manager and right click and select end task. Restart the game.

[哈哈哈哈]

Originally posted by Aulterson:

Try running the game and then go to your desktop. Once you're there, open the Task Manager and right click and select end task. Restart the game.

Hi, thanks for your time - I've refunded the game now, however I was running this on Manjaro (Arch, Linux).

[linuxgnuwu]

Originally posted by nachos:

Originally posted by Aulterson:

Try running the game and then go to your desktop. Once you're there, open the Task Manager and right click and select end task. Restart the game.

Hi, thanks for your time - I've refunded the game now, however I was running this on Manjaro (Arch, Linux).

Try this:

Possible Linux crash fix.
Although this fix may not work for everyone out there, it did work for me.
Step 1) Close steam.
Step 2) Open a terminal and type this:

LD_PRELOAD='/usr/lib/x86_64-linux-gnu/libstdc++.so.6 /lib/x86_64-linux-gnu/libgcc_s.so.1 /usr/lib/x86_64-linux-gnu/libxcb.so.1' steam

Now steam will restart and you can launch the game. You can ofc put this into a bash file and make it executable; that way you won't have to remember it.
If this doesn't fix it, I can't help...

(I also have turned off steam overlay and cloud).

The way I found this out was by closing steam and launching steam through a terminal and looking at the output when the game crashes. And apparantly it's a segfault (memory access issue), but before that I'd get a lot of LD_PRELOAD errors. I simply googled that and found an article with this command.

Hopefully this will work for most people.

from: https://steamcommunity.com/app/477160/discussions/1/1728701877466093693/

[哈哈哈哈]

Originally posted by linux gnu ru:

Originally posted by nachos:

Hi, thanks for your time - I've refunded the game now, however I was running this on Manjaro (Arch, Linux).

Try this:

Possible Linux crash fix.
Although this fix may not work for everyone out there, it did work for me.
Step 1) Close steam.
Step 2) Open a terminal and type this:

LD_PRELOAD='/usr/lib/x86_64-linux-gnu/libstdc++.so.6 /lib/x86_64-linux-gnu/libgcc_s.so.1 /usr/lib/x86_64-linux-gnu/libxcb.so.1' steam

Now steam will restart and you can launch the game. You can ofc put this into a bash file and make it executable; that way you won't have to remember it.
If this doesn't fix it, I can't help...

(I also have turned off steam overlay and cloud).

The way I found this out was by closing steam and launching steam through a terminal and looking at the output when the game crashes. And apparantly it's a segfault (memory access issue), but before that I'd get a lot of LD_PRELOAD errors. I simply googled that and found an article with this command.

Hopefully this will work for most people.

from: https://steamcommunity.com/app/477160/discussions/1/1728701877466093693/

Thanks for the reply and help, I've refunded the game now but will rebuy and try again and report back, thanks regardless for your time friend :)

[Tempest]

i have this problem where it crashes once the narrator starts speaking, i'm on ubuntu, none of those fixed my issue, i just bought the game and i really want to play it!

[哈哈哈哈]

Originally posted by Hey Mike, I miss you man:

i have this problem where it crashes once the narrator starts speaking, i'm on ubuntu, none of those fixed my issue, i just bought the game and i really want to play it!

Am on Linux too, it's sad to hear these suggestions haven't worked for you (I was on Manjaro/Arch). Please keep me up to date with any news because I'd rebuy this in a second if there was a fix.

Although with that said, my game really crashes 'randomly', sometimes when I open a door, sometimes when an event starts (voice over talking) - I cannot place my finger on it or make rhyme or reason either.. Best of luck friend.

[✯ J_Tanzanite ✯]

Well the reason always is a segfault, which is when a process attempts to read or write to a memory address it does not have access to.
And last time I tested this, it attempts to read memory address NULL. Which is what malloc() will return apron an error. So these crashes could be because of no error checking having been done.

I am not certain that it is address NULL it always tries to access though, nor am I certain that it segfaults for everyone, but it seems to be this issue for everyone.

[哈哈哈哈]

Originally posted by TheLazyCWriter:

Well the reason always is a segfault, which is when a process attempts to read or write to a memory address it does not have access to.
And last time I tested this, it attempts to read memory address NULL. Which is what malloc() will return apron an error. So these crashes could be because of no error checking having been done.

I am not certain that it is address NULL it always tries to access though, nor am I certain that it segfaults for everyone, but it seems to be this issue for everyone.

Forgive my ignorance but does this mean it's an issue that the developer need to address and not an issue with hardware/software installed?

Thanks for your reply and time

[✯ J_Tanzanite ✯]

Originally posted by nachos:

Forgive my ignorance but does this mean it's an issue that the developer need to address and not an issue with hardware/software installed?
Thanks for your reply and time

You're correct, this is a programming mistake, not the fault of the hardware.

To explain what segfaults means in easier terms, every process uses some memory in RAM. This can be used to load game files such as sound, video, textures etc.

When a process needs more memory, it will do a function call asking the operating system for premission to use more RAM. Two of the most notibly function calls are malloc() and mmap().
When they are called, the the operating system will either give more memory or deny it (deppending on whether you have enough ram, the requested size of memory is too large, etc).

And the way the operating system tells the process it's been denied more memory, is to return to the process an address that no process will ever have access to. In the case of malloc(), it's NULL (Memory Address zero). On the other hand, if the operating system accepts the request, it will return an address in RAM to the newly accepted space.

It is the job of the programmer to check if he was denied more memory or not, this is called error checking (not limited to this though).
In the case of "Human: Fall Flat", it seems like malloc() returned NULL and the process still tired to access it anyway. Linux (And other operating systems) will notice this and send a kill signal to the application immediately. This kill signal in particular is called Segmentation Fault, and processes only get this if they try to access memory they do not have premission to.


My explanation here is heavily toned down for simplicity, you can get segfaults even without using malloc() or mmap(); granted you try accessing memory you don't have premission to.

It is also entirely possible that "Human: Fall Flat" gets a segfault due to a bug in the game.
Another disclaimer is that I cannot look at the game's source code and find where the bug is or what the issue in particular is, so it could also be the case that malloc() was never called in the first place and that it isn't NULL it tries to access; I simply can't know for sure.

As far as I know, this game uses the Unity engine, and if it is the engine that crashes, the developer cannot fix it. I hope this isn't the case.

I could try to use GDB and find out exactly what it tries to access and where the bug is, but, I don't think I have the premission of the developer to do this, and this is something I rather not spend time on.

[哈哈哈哈]

Originally posted by TheLazyCWriter:

Originally posted by nachos:

Forgive my ignorance but does this mean it's an issue that the developer need to address and not an issue with hardware/software installed?
Thanks for your reply and time

You're correct, this is a programming mistake, not the fault of the hardware.

To explain what segfaults means in easier terms, every process uses some memory in RAM. This can be used to load game files such as sound, video, textures etc.

When a process needs more memory, it will do a function call asking the operating system for premission to use more RAM. Two of the most notibly function calls are malloc() and mmap().
When they are called, the the operating system will either give more memory or deny it (deppending on whether you have enough ram, the requested size of memory is too large, etc).

And the way the operating system tells the process it's been denied more memory, is to return to the process an address that no process will ever have access to. In the case of malloc(), it's NULL (Memory Address zero). On the other hand, if the operating system accepts the request, it will return an address in RAM to the newly accepted space.

It is the job of the programmer to check if he was denied more memory or not, this is called error checking (not limited to this though).
In the case of "Human: Fall Flat", it seems like malloc() returned NULL and the process still tired to access it anyway. Linux (And other operating systems) will notice this and send a kill signal to the application immediately. This kill signal in particular is called Segmentation Fault, and processes only get this if they try to access memory they do not have premission to.


My explanation here is heavily toned down for simplicity, you can get segfaults even without using malloc() or mmap(); granted you try accessing memory you don't have premission to.

It is also entirely possible that "Human: Fall Flat" gets a segfault due to a bug in the game.
Another disclaimer is that I cannot look at the game's source code and find where the bug is or what the issue in particular is, so it could also be the case that malloc() was never called in the first place and that it isn't NULL it tries to access; I simply can't know for sure.

As far as I know, this game uses the Unity engine, and if it is the engine that crashes, the developer cannot fix it. I hope this isn't the case.

I could try to use GDB and find out exactly what it tries to access and where the bug is, but, I don't think I have the premission of the developer to do this, and this is something I rather not spend time on.

Thank-you for your indepth and detailed reply - I'm pretty sure I understood most of what you put and I'm an idiot for the most part (always have been, not being belligerent to myself).

I hope the developer sees this and it is (somehow) some use to them in debugging.

I can't offer you anything other thank thanks and gratitude but I assure you you'vr got it all. All the best, thanks again for your time and effort friend :)

[✯ J_Tanzanite ✯]

Hehe, no problem. I'm no expert at these kinds of things, I'm actually pretty bad at programming myself. But you learn as you go. I'm sure the developer will get this sorted out after a while, development takes time after all.