Unity-2018.1.0f2 Crashes on start up.

I have been trying to get the 2018 versions running on linux for a while now, without success.
I do have an AMD cpu and according to the download post, if I have "__do_global_ctors_aux" in an error log then I am not alone. I don't even get far enough for it to create an error log.
The error I get is "Illegal instruction (core dumped)". So I checked out the core dump file and the error is says I am getting is :

Program terminated with signal SIGILL, Illegal instruction.
#0 0x00007ff76dc1e761 in MATH::Crc32Generator::Crc32Generator (
this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
53 /vagrant_share/openrl/Code/Math/Source/crc.cpp: No such file or directory.

I have no clue what this means so I am hoping someone does.
I have installed windows and tried that version and it runs with out a problem and no problem with the linux 2017 versions.

I am using Ubuntu 18.04 64bit, AMD Athlon ii x4 640 cpu, Nvidia GeForce GTX 1060, and 10GB of ram.

 

I also get an "Illegal instruction" error when running Unity-2018.1.0f2. When I check the logs I see this:

Unity[6668] trap invalid opcode ip:7fe492046761 sp:7fffd210ec18 error:0 in libRL.so[7fe491fa9000+c58000]

I suspect this is caused by an instruction (opcode) that is not available on my CPU.

I have no problems running Unity-2017.4.2f2.

I'm using Linux Mint 18.2 Cinnamon 64-bit, AMD Phenonm II X4 940 , Nvidia GeForce GTX 1060 and 8Gb Ram

 

I'm running Arch Linux and I have the same exact problem with the same error. I also have an AMD CPU (Phenom II X4 965 Processor) but an nvidia video card. I can run Unity-2017... but not Unity-2018...

 

Can somebody who's experiencing this try out the build from
https://beta.unity3d.com/download/4a2b719b3366/public_download.html ?

 

Just tried it, installed Unity-2018.2.0b5, but unfortunatly still wont run. Same error as before:

Unity[29810] trap invalid opcode ip:7f8a176e0761 sp:7fffc4f993d8 error:0 in libRL.so[7f8a17643000+c58000]

 

Thanks, we'll keep digging.

 

All right, another test build: https://beta.unity3d.com/download/4700226dc42d/public_download.html

 

With this build I can get it to start but then the bug reporter shows up.
Here is the errors:

[0601/161441:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

Gtk-Message: 16:14:41.660: GtkDialog mapped without a transient parent. This is discouraged.

[0601/161441:ERROR:renderer_main.cc(227)] Running without renderer sandbox

[0601/161441:ERROR:gpu_process_transport_factory.cc(402)] Failed to establish GPU channel.

[0601/161443:ERROR:connection.cc(1060)] DOMStorageDatabase sqlite error 14, errno -2: unable to open database file, sql: -- sqlite3_open()

[0601/161443:ERROR:dom_storage_database.cc(163)] Unable to open DOM storage database at /home/atom/.config/unity3d/Unity/Browser/Cache/Local Storage/file__0.localstorage error: sql::Connection has no connection.
​

 

What do you get with your core dump this time?

 

Here is what I am now getting in the coredump

Core was generated by `./Unity'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

 

ok, the new one you have posted at least starts but it can't load up projects.
I have an older intel dual core CPU and a geforce card.
The 2017.2 version runs fine.

 

I tried it with the Unity-2018.2.0b7 I can create a new project but when it tries to load the project it crashes.

Here is the info from the coredump:

Here is the info from the error log:

 

Can you post the core dump itself? Or at least the entire backtrace? (Type backtrace at the gdb prompt.)

 

I cannot get it to create a core dump file anymore. I know core dump is enabled because I used this command "sleep 10 & killall -SIGSEGV sleep" and it did create a core dump.

I wonder if it has something to do with it creating new projects for the 2018.2.0.b3 and not the 2018.2.0.b7. I do get an error pop up telling me about opening projects in a non-matching editor installation. If I click the quit button on this pop up I don't get the bug reporter. So the error only occurs when trying to open the project.

Here is the error log from the Unity Bug Reporter file:

 

2018.2.0b5 (Phenom II 1090T)

Code (csharp):

1.  
2. Program received signal SIGILL, Illegal instruction.
3. 0x00007fffefac1761 in MATH::Crc32Generator::Crc32Generator (
4.     this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
5. 53   /vagrant_share/openrl/Code/Math/Source/crc.cpp: No such file or directory.
6. (gdb) backtrace
7. #0  0x00007fffefac1761 in MATH::Crc32Generator::Crc32Generator (this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
8. #1  0x00007fffefac1761 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:40
9. #2  0x00007fffefac1761 in _GLOBAL__sub_I_crc.cpp(void) ()
10.     at /vagrant_share/openrl/Code/Math/Source/crc.cpp:168
11. #3  0x00007ffff7fe45a3 in  () at /lib64/ld-linux-x86-64.so.2
12. #4  0x00007ffff7fd50ca in  () at /lib64/ld-linux-x86-64.so.2
13. #5  0x0000000000000001 in  ()
14. #6  0x00007fffffffe93f in  ()
15. #7  0x0000000000000000 in  ()
16. (gdb)
17.  

2018.2.0b7

Code (csharp):

1.  
2. Thread 86 "Unity" received signal SIGPWR, Power fail/restart.
3. [Switching to LWP 16238]
4. 0x00007ffff5db8607 in accept () from /usr/lib/libpthread.so.0
5. (gdb) backtrace
6. #0  0x00007ffff5db8607 in accept () at /usr/lib/libpthread.so.0
7. #1  0x00007fff9e62c2f3 in  ()
8.     at /home/domino/Unity-2018.2.0b7/Editor/Data/Mono/MonoEmbedRuntime/libmono.so
9. #2  0x00007fff9e632195 in  ()
10.     at /home/domino/Unity-2018.2.0b7/Editor/Data/Mono/MonoEmbedRuntime/libmono.so
11. #3  0x00007fff9e70bed3 in  ()
12.     at /home/domino/Unity-2018.2.0b7/Editor/Data/Mono/MonoEmbedRuntime/libmono.so
13. #4  0x00007fff9e72c385 in  ()
14.     at /home/domino/Unity-2018.2.0b7/Editor/Data/Mono/MonoEmbedRuntime/libmono.so
15. #5  0x00007ffff5dae6ca in  () at /usr/lib/libpthread.so.0
16. #6  0x00007fffef7a6cef in clone () at /usr/lib/libc.so.6
17. (gdb)
18.  

Let me know if you need a full dump, my bug report was closed as a duplicate (of one dated after mine) but I'm still affected and keeping an eye on progress here. I'm running Solus so I'll understand if you need an Ubuntu user to do it instead.

 

Is this from the core dump, or from running normally with gdb?
SIGPWR is used internally by mono, and shouldn't cause a problem during normal use.
(To run in gdb without stopping on these, you can run the following in gdb, or add to ~/.gdbinit )

Code (csharp):

1. handle SIGXCPU SIG33 SIG35 SIG36 SIG37 SIGPWR SIGPIPE nostop noprint

 

From running normally with gdb. Automatic core dumps are disabled in Solus (for security purposes I think).
Thanks for the tip on ignoring those signals. Here's a new backtrace from 2018.2.0b7.

Code (csharp):

1.  
2. Thread 1 "Unity" received signal SIGILL, Illegal instruction.
3. 0x00007fff9cc0671b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
4.    from /home/domino/Unity-2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
5. (gdb) backtrace
6. #0  0x00007fff9cc0671b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
7.     at /home/domino/Unity-2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
8. #1  0x00007fff9c8d74f9 in _GLOBAL__sub_I_bspline_curve.cpp ()
9.     at /home/domino/Unity-2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
10. #2  0x00007fff9ccda566 in __do_global_ctors_aux ()
11.     at /home/domino/Unity-2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
12. #3  0x00007fff9c8c8ec7 in _init ()
13.     at /home/domino/Unity-2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
14. #4  0x0000000000000000 in  ()
15. (gdb)
16.  

 

Ok, that's helpful, thanks!

 

Hmm.. An extension / plugin, so I wondered if it'll run without it. I tried deleting the libaudiopluginresonanceaudio.so & .meta and 2018.2.0b7 editor now launches successfully.

The test project created during the crash is stuck at version 2018.2.0b3 and doesn't seem to save the update when opened and saved in b7, but a new test project has the correct version.

 

That's great news! Can anybody else confirm that removing Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so resolves their issues?

 

2018.1.5f1 is showing the same error as 2018.2.0b5 - this halts earlier in the startup than 2018.2.0b7 and doesn't get to the resonance audio issue.

Code (csharp):

1.  
2. Program received signal SIGILL, Illegal instruction.
3. 0x00007fffefd17761 in MATH::Crc32Generator::Crc32Generator (this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
4. 53   /vagrant_share/openrl/Code/Math/Source/crc.cpp: No such file or directory.
5. (gdb) backtrace
6. #0  0x00007fffefd17761 in MATH::Crc32Generator::Crc32Generator (this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
7. #1  0x00007fffefd17761 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:40
8. #2  0x00007fffefd17761 in _GLOBAL__sub_I_crc.cpp(void) ()
9.     at /vagrant_share/openrl/Code/Math/Source/crc.cpp:168
10. #3  0x00007ffff7fe45a3 in  () at /lib64/ld-linux-x86-64.so.2
11. #4  0x00007ffff7fd50ca in  () at /lib64/ld-linux-x86-64.so.2
12. #5  0x0000000000000001 in  ()
13. #6  0x00007fffffffe93f in  ()
14. #7  0x0000000000000000 in  ()
15. (gdb)
16.  

 

I removed the libaudiopluginresonanceaudio.so and the meta file with it and it seemed to fix the issue. I have not played around yet but I can load the editor now.

 

I can also confirm removing the above so file fixed the crash for me on my old rusty notebook: AMD Turion(tm) X2 Dual-Core Mobile RM-70. Thanks.

 

2018.1.6.f1 has the same problem as other 2018.1.x versions.

Code (csharp):

1. Program received signal SIGILL, Illegal instruction.
2. 0x00007fffefd16761 in MATH::Crc32Generator::Crc32Generator (
3.     this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
4. 53   /vagrant_share/openrl/Code/Math/Source/crc.cpp: No such file or directory.
5. (gdb) backtrace
6. #0  0x00007fffefd16761 in MATH::Crc32Generator::Crc32Generator (this=<optimized out>) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:53
7. #1  0x00007fffefd16761 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /vagrant_share/openrl/Code/Math/Source/crc.cpp:40
8. #2  0x00007fffefd16761 in _GLOBAL__sub_I_crc.cpp(void) ()
9.     at /vagrant_share/openrl/Code/Math/Source/crc.cpp:168
10. #3  0x00007ffff7fe45a3 in  () at /lib64/ld-linux-x86-64.so.2
11. #4  0x00007ffff7fd50ca in  () at /lib64/ld-linux-x86-64.so.2
12. #5  0x0000000000000001 in  ()
13. #6  0x00007fffffffe93f in  ()
14. #7  0x0000000000000000 in  ()
15. (gdb)

 

Ok, another test build - can you verify that the resonance audio plugin doesn't trigger the crash?
https://beta.unity3d.com/download/473c9eab9ba4/public_download.html

 

Nope, still crashes for me.

Code (csharp):

1. Thread 1 "Unity" received signal SIGILL, Illegal instruction.
2. 0x00007fff9811271b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
3.    from /home/domino/Unity-2018.2.0b10/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
4. (gdb) backtrace
5. #0  0x00007fff9811271b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
6.     at /home/domino/Unity-2018.2.0b10/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
7. #1  0x00007fff97de34f9 in _GLOBAL__sub_I_bspline_curve.cpp ()
8.     at /home/domino/Unity-2018.2.0b10/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
9. #2  0x00007fff981e6566 in __do_global_ctors_aux ()
10.     at /home/domino/Unity-2018.2.0b10/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
11. #3  0x00007fff97dd4ec7 in _init ()
12.     at /home/domino/Unity-2018.2.0b10/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
13. #4  0x0000000000000000 in  ()
14. (gdb)

 

This new test still gives me errors. Now in the terminal it does not crash due to illegal instruction but crashes with an "Aborted (core dump)" but no core is generated. I do get the Unity debug tool popup, so here is the error log from that. Deleting libaudiopluginresonanceaudio.so and the meta file still allows me to run without an issue.

 

2018.2.0f1 also crashes. Is it normal to ignore Priority 2 bugs and do final releases regardless?

Code (csharp):

1. Thread 1 "Unity" received signal SIGILL, Illegal instruction.
2. 0x00007fff981ac71b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
3.    from /home/domino/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
4. (gdb) backtrace
5. #0  0x00007fff981ac71b in embree::PrecomputedBSplineBasis::PrecomputedBSplineBasis(int) ()
6.     at /home/domino/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
7. #1  0x00007fff97e7d4f9 in _GLOBAL__sub_I_bspline_curve.cpp ()
8.     at /home/domino/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
9. #2  0x00007fff98280566 in __do_global_ctors_aux ()
10.     at /home/domino/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
11. #3  0x00007fff97e6eec7 in _init ()
12.     at /home/domino/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so
13. #4  0x0000000000000000 in  ()
14. (gdb)

Is the libaudiopluginresonanceaudio.so built differently than the open source one? I just built that, copied it over the 2018.2.0f1 one, and the editor launches without crashing. The install version was only 11Mb compared to 23Mb for the one I built.

Code (csharp):

1. #!/bin/bash
2. git clone https://github.com/resonance-audio/resonance-audio
3. ./resonance-audio/third_party/clone_core_deps.sh
4. ./resonance-audio/third_party/clone_build_install_unity_deps.sh
5. ./resonance-audio/build.sh -t=UNITY_PLUGIN
6. cp ./resonance-audio/install/unity/Assets/ResonanceAudio/Plugins/x86_64/libaudiopluginresonanceaudio.so ~/Unity-2018.2.0f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so

 

I understand your frustration, but since Linux isn't an official editor platform yet...

The one shipped with Unity is built by google as part of https://github.com/resonance-audio/resonance-audio-unity-sdk
I'll investigate whether we can help resolve this by tweaking the plugin build.

 

Obviously I don't know the internal circumstances, it just struck me that it avoided the "why isn't there a Linux final yet?" question which might have resulted in more resources for the Linux team (like a Phenom PC for testing). With issues like the case sensitive shader filename bug in first 2018 release, it's obvious that some teams in Unity don't test with Linux. Glossing over problems doesn't seem like a path to an official release when Linux awareness seems to be one of the things that needs work.

Ok thanks. If I could replicate the faulty build I could isolate the cause for you.

 

I suspect that the embree cmake configuration is detecting what's supported on your cpu and thus avoiding the problem when you build locally.
Can you try https://oc.unity3d.com/index.php/s/NA28ke99TG31qKI ?

 

Tried it in 2018.2.0f1 and no crash.

 

Great, I'll try this one in the next 2018.2 build

 

2018.2.0f2 opens the editor without a crash.

I am getting other issues

Spoiler: such as

"Failed setting thread niceness (priority) to 0 due to EACCES (errno 13) violation. Lowering niceness (raising priority) requires CAP_SYS_NICE or superuser."

Which lead to this strangeness:

Code (csharp):

1. domino@desktop1 ~/Unity-2018.2.0f2/Editor $ sudo setcap 'cap_sys_nice=eip' Unity
2. domino@desktop1 ~/Unity-2018.2.0f2/Editor $ ./Unity
3. ./Unity: error while loading shared libraries: libfbxsdk.so: cannot open shared object file: No such file or directory

I'll need to investigate further but am guessing this is due to Solus having a stronger approach to security than Ubuntu as the file does exist in Editor/Data/Tools

Is there a list of capabilities Unity needs?

But the crash on startup is fixed. Thanks Tak!

 

The thread niceness thing is just a warning about setting a priority for a worker thread higher than the system default, but it shouldn't affect operation.

 

Not exactly the same but we have started getting this:

Code (CSharp):

1. Plugins: Couldn't open /2018.2.4f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so, error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (r
2. equired by /2018.2.4f1/Editor/Data/UnityExtensions/Unity/VR/Linux64/libaudiopluginresonanceaudio.so)

Code (CSharp):

1. /lib64/libstdc++.so.6 -> libstdc++.so.6.0.19