SIGSEGV crash on Application.Quit()

I am getting a crash upon calling Application.Quit() in the Linux player. I was able to reproduce this in a tutorial project (http://u3d.as/mWH) by adding a call to Application.Quit() upon pressing ESC, so it doesn't appear to be specific to my project. This was in a game built from the Linux Unity editor, version 5.4.1f1, on Ubuntu 16.04.

 

Found this via Google.

I have the same issue building for windows 10 standalone on mac using unity version 5.4.2p2.
Happens only once after system boot when starting and quitting the app for the first time.

 

We're investigating a similar issue. If you have access to Unity 5.4.2, can you verify that you get the same behavior with this build? http://files.unity3d.com/levi/LinuxStandaloneSupport-5.4.2f2+exitcrash.zip

This sounds like an unrelated problem. Could you file a bug report with your project and steps to reproduce?

 

Will do, thanks!

 

I am still experiencing this with players made from Unity 5.4.3xf1. Would it still be beneficial to test with the build above?

 

We also get a SIGSEGV on Application.Quit() on Linux x86_64 builds using Unity 5.5.0p3

Player.log says:

Player is already running

(Filename: Line: 457)
Stacktrace:
Native stacktrace:
/home/player/Assets/.../58359a1baeee02000f91b244/..._StandaloneLinux64_Data/Mono/x86_64/libmono.so(+0x91a46) [0x7f06b4230a46]
/home/player/Assets/.../58359a1baeee02000f91b244/..._StandaloneLinux64_Data/Mono/x86_64/libmono.so(+0x348e4) [0x7f06b41d38e4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x113e0) [0x7f06b9ae43e0]
/home/player/Assets/.../58359a1baeee02000f91b244/UnityGame() [0xf30b6d]
/lib/x86_64-linux-gnu/libc.so.6(+0x39ff8) [0x7f06b82daff8]
/lib/x86_64-linux-gnu/libc.so.6(+0x3a045) [0x7f06b82db045]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf7) [0x7f06b82c1837]
/home/player/Assets/.../58359a1baeee02000f91b244/UnityGame() [0x46f7a5]
Debug info from gdb:
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

 

Strange, my crash apparently no longer occurs in builds from 5.5.0xp1. We're also building for Linux x86_64.

 

This is from a second player that was launched in "single instance" mode - not related to the original issue.