Linux game stops responding

Development Platform & Builds
, , , , , ,
1

I am running 4.6.1 on windows 8.1 and packing on windows.

My game starts with and empty level and does nothing and is responding at this time it should not or write anything

If I press a key and spawn widgets , the game becomes not-responding.

If I try to create a save game, the game becomes not-responding.

on the title screen it says GLSL_150

glxinfo | grep “OpenGL version”

3.0 mesa 10.3.0

when I launch via the terminal:

Using binned
FMallocCrash overhead is 3780608 bytes
4.6.1-0+UE4 7038 3077 412 0

my Linux setup is

14.04 LTS with no swap file(drive?)
8GB ram
intlel i3 with gpu HD4400

2

I can provide a steam key for testing

Also a previous build (current steam build) becomes not responding when [remove from parent] was used to close a widget ( the game is starting with beginplay>create windget> addtoviewport )

3

Hey Midnight640-

I am going to need a bit more information from you before I begin looking into this issue. Could you attach your logs to this thread where you are seeing the error occur? Also, would there be a couple of steps that I may use to recreate this issue internally?

Any additional information would be greatly appreciated.

Cheers

4

Which logs ? Game doesn’t launch CrashReportClient. It just goes gray…
I can attach the build log if this will help.
My whole project is like 4gb but the steam download is around 500mb so if you give me an email or other PM way I will give a code .

It is interesting that I cant get a stable launch now even when I replicate the conditions of the steam build. It just goes gray. The problem is not in steam since it does it on my pc. I am not sure if this has to do with the openGL version I am running since only nvidia and amd support 4.3 and my HD graphics is running 3.0

5

Another idea, I am just copy pasting my dx11 project to another machine for linux compiling . The DX11 version has distance field shadows and AO enabled so since they dont work on linux i will try to wipe the editor settings back to default and see if this will help

Also my 4.6.1 from source wants to convert my 4.6.1 from launcher game which is strange

6

If you open the project in the editor and run a standalone game do you get the same unresponsiveness as the packaged version? The project logs from the Saved->Logs folder of the project will help give an idea of what’s happening? Let me know if there is any success after removing the distance field shadows. One last test to run would be to check if the same unresponsiveness happens when running a game packaged for Windows rather than Linux

7

In windows editor it runs like a dream. I am waiting it to finish compiling also does openGL support Txaa and Fxaa on the web it seem that they are not that easy to integrate. I will compile now and update you with logs

8

500mb of logs turned into a 8mb zip …

anyway
https://drive.google.com/file/d/0BwHX-PingVgiMnlFclZzMTN4cWc/view?usp=sharing

no change still “not responding” I will now disable all the plugins that are turned on by default and report back

no change again

9

Just an idea, but run your game thorough gdb then ‘break’ it when it hangs and do a backtrace (bt). It should give some clues of the method it’s stuck in.

10

sweet mother of jesusus ! Sory for the delay i was gamejamming

Here is the gdb log

11

(gdb) r deORBIT2
Starting program: /home/li/.local/share/Steam/steamapps/common/deORBIT/deORBIT2/Binaries/Linux/deORBIT2 deORBIT2
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
Using binned.
FMallocCrash overhead is 3780608 bytes
4.6.1-0+UE4 7038 3077 413 0
[New Thread 0x7ffff7f32700 (LWP 3360)]
[New Thread 0x7ffff7ebb700 (LWP 3361)]
[New Thread 0x7ffff584d700 (LWP 3362)]
[New Thread 0x7fffe9e87700 (LWP 3363)]
[Thread 0x7fffe9e87700 (LWP 3363) exited]
[New Thread 0x7ffff6972700 (LWP 3364)]
[New Thread 0x7ffff68a3700 (LWP 3365)]
[New Thread 0x7fffe9e87700 (LWP 3366)]
[New Thread 0x7fffece64700 (LWP 3367)]
[New Thread 0x7fffecdad700 (LWP 3368)]
[Thread 0x7fffecdad700 (LWP 3368) exited]
[New Thread 0x7fffecdad700 (LWP 3369)]
[New Thread 0x7fffec5ac700 (LWP 3370)]
[New Thread 0x7fffec19b700 (LWP 3371)]
[New Thread 0x7fffed464700 (LWP 3372)]
[Thread 0x7fffece64700 (LWP 3367) exited]
[Thread 0x7fffe9e87700 (LWP 3366) exited]
[Thread 0x7fffed464700 (LWP 3372) exited]
[Thread 0x7fffec19b700 (LWP 3371) exited]
[New Thread 0x7fffec19b700 (LWP 3373)]
[New Thread 0x7fffed464700 (LWP 3374)]
[Thread 0x7fffed464700 (LWP 3374) exited]
[Thread 0x7fffec19b700 (LWP 3373) exited]
[New Thread 0x7fffec19b700 (LWP 3375)]
[New Thread 0x7fffed464700 (LWP 3376)]
[Thread 0x7fffed464700 (LWP 3376) exited]
[Thread 0x7fffec19b700 (LWP 3375) exited]
[New Thread 0x7fffec19b700 (LWP 3377)]
[New Thread 0x7fffed464700 (LWP 3378)]
gdb bt
[Thread 0x7fffec19b700 (LWP 3377) exited]
[Thread 0x7fffec5ac700 (LWP 3370) exited]
[Thread 0x7fffecdad700 (LWP 3369) exited]
[Thread 0x7ffff6972700 (LWP 3364) exited]
[Thread 0x7ffff584d700 (LWP 3362) exited]
[Thread 0x7ffff7ebb700 (LWP 3361) exited]
[Thread 0x7ffff7f32700 (LWP 3360) exited]
[Thread 0x7ffff7fd97c0 (LWP 3356) exited]
[Thread 0x7ffff68a3700 (LWP 3365) exited]

12

Just tested it with my gameJam game , It starts fine and the stall occurs when I execute console command (set res … r.screenpercentage etc)
and when I change levels. removing and adding widgets to viewports does not bother the game. I am sure the problem is in my editor. What is the ETA of 4.7 should I wait for it or try to rebuild 4.6 now ( in the coming week )

13

There does not seem to be a crash backtrace, as all threads exited cleanly?

14

if no one with a working linux wants to test the game i guess I will have to rebuild the editor from git.

edit 21st Jan : I am going to rebuild the engine from git ( 4.6) and hope that this fixes the problem , will update you asap

15

It turns out that my HD4400 had only 32 mb of ram.
I saw it in the bios and made it 512, I also re installed the linux to have a swap drive and the game runs fine
A lot lower fps than the same setup on windows but … not the engine’s fault.