0
Completed - Resolved

Crash : Segmentation fault

YS1 3 years ago updated by Lee "Noontide" Moon (Designer & Community Manager) 3 years ago 7

Just after beginning playing a new map (not in the campaign), WFTO crashed with a segmentation fault. In fact, this caused the whole system to cease to function, as the GPU ceased operation.

Here is the crash report. Your system does not seem to allow posting the 4,3MB crash report, without however writing out any message about this, which is very annoying.

Player.log

Game Version:
Steam Public
Platform:
Linux

This happened a second time, with the same map (Fire Chiasm).

Pending Customer

Output log?

Accepted

@Nutter: There is a Player.log attached.

Hey YS1,
it seems it happened after our UI middleware failt to initinialize correctly in a long loop of death.
---------------------

(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)

[Coherent Browser] (Error) glTexSubImage2D failed with error 1280 (W/H 1920x1200; Format GL_BGRA)

(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)

[Coherent Browser] (Error) Unable to update texture for view 0

---------------------

However there are some known issues with OSx and Linux which got fixed and we updated the UI middleware to a newer version for the coming soon patch v1.4.2.
We hope it will fix this problem for you (and multiple others).


Obviously there was an log attached, I was just wondering if he had a log for the second occurrence to help narrow down the issue.

Sorry for the misunderstanding (however, understanding an incomplete sentence is quite difficult).


I tried the map with the latest patch ; it works. I do not know if this is conclusive or the problem just appears in circumstances that do not exist in every game.

Completed - Resolved

Great to hear, we'll close this down for now but if you have any more problems please get in touch!