5.2 sporadic SIGSEGV crash in linux headless builds

Scripting C# & .NET
1

I’m experiencing a SIGSGV crash since updating to 5.2, which happens not all the time, but around 1 of 3 times when starting the build. I still have to build a smaller repro, but maybe somebody here already has an idea what it could be…?

OS: Ubuntu 14.04
Architecture: x64

Stacktrace:


Native stacktrace:

    /home/krautscape/krautscape/node/bin/game/Krautscape_Data/Mono/x86_64/libmono.so(+0x915e6) [0x7f1e16c3b5e6]
    /home/krautscape/krautscape/node/bin/game/Krautscape_Data/Mono/x86_64/libmono.so(+0x3483b) [0x7f1e16bde83b]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f1e181b7340]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0xd1a8d0]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0xd1adef]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843a20]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843839]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843975]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843a06]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843839]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843975]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843a06]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x843839]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x845207]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x842be9]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0xd01dd1]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x46f26a]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x7198f2]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x715bd3]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x716714]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x5ca827]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x7257f4]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x45e213]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1e173daec5]
    /home/krautscape/krautscape/node/bin/game/Krautscape.x86_64() [0x46684d]

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.
=================================================================
2

Same problem here.
3 out of 5 times crashed on CentOS7.
Windows works fine.

3

I finally reported the bug with repro, case id: 732667

Could somebody of Unity have a look at it?

4

Any ideas what it could be? Could somebody from Unity look at the bug report?

5

Hi folks! I’m looking into your bug status right now, but I’m also going to move this to the L̶i̶n̶u̶x̶ Multiplayer Networking part of the forums :smile:

  • EDIT - Its being worked on actively by QA to reproduce and find out what is causing your issues :smile: That is good news! :smile:
2 Likes
6

Great! Let me know if you need any more information about the issue.

1 Like
7

What is the most recent version of Unity Editor that creates builds with this issue? 5.2.1p2?

8

I had it with p1 and f1 last time I checked.

9

I tried 3 times today with a fresh Unity 5.2.1p2 build.
It crashed 3/3 times under Linux.

Works perfect under Windows.

@any_user : [“I finally reported the bug with repro, case id: 732667”]

Would you mind posting the full link to the fogbugz issue? So we can all look up the progress.
Thanks in advance.

10

there’s no progress, i never received an update. will post here if i get one.

@holliebuckets_1 do you know if there is an update about this issue?

for us this crash means it’s impossible to update to 5.2 in two projects which use linux servers…

11

Are people seeing this with 5.2.1p3?

12

I investigated a bit. It still happens in 5.2.1p3.

I made a new repro that consists of just two scenes. In Start of a script in scene 1, scene 2 is loaded. The first scene also includes a canvas with an image inside. Starting a build with just this inside is enough to trigger the crash. I reported it as a new case with more precise description as case 734921.

It might be somehow connected to this:

But I’m only able to reproduce it in linux headless builds, not in a Mac build or in the Editor, so I’m not completely sure if it’s the same.

1 Like
13

any update on this? It’s still not fixed in 5.2.3 and nobody looked at the bug report…

edit: the workaround of removing all canvases in the first scene works so far, but that’s not really how it should be.

14

Same here. Lot of users reporting their dedicated servers don’t work anymore with the latest release (Unity 5.2.3f1 vs 5.1.1 in our previous release). All get that stack trace as shown in the OP.
It does work on some machines though, for example both my own desktop and dedi.

Also could maybe be related to sound changes (maybe previous headless builds properly disabled audio output which does make sense but the newer ones do not?). Reason: quite a bunch of the users reported it working after installing pulseaudio.

@Unity: Any updates on this one?

Regards,
Chris

15

Hi, guys

Same problem found on centos 7.1 and unity 5.3.1f1.
Does anyone has any progress about this?

Native stacktrace:

/tmp/Demo-HeadLess/DemoLinux64_Data/Mono/x86_64/libmono.so(+0x915e6) [0x7f57acda45e6]
/tmp/Demo-HeadLess/DemoLinux64_Data/Mono/x86_64/libmono.so(+0x347fc) [0x7f57acd477fc]
/lib64/libpthread.so.0(+0xf100) [0x7f57ae31a100]
./DemoLinux64() [0x46a5ae]
./DemoLinux64() [0x46a916]
./DemoLinux64() [0x46a988]
./DemoLinux64() [0x46826f]
./DemoLinux64(_Znwm+0x45) [0x4687b5]
/lib64/libstdc++.so.6(_ZNSs4_Rep9_S_createEmmRKSaIcE+0x59) [0x7f57adeb8c69]
/lib64/libstdc++.so.6(_ZNSs12_S_constructIPKcEEPcT_S3_RKSaIcESt20forward_iterator_tag+0x21) [0x7f57adeba521]
/lib64/libstdc++.so.6(_ZNSsC2EPKcRKSaIcE+0x38) [0x7f57adeba958]
./DemoLinux64() [0x87c6ca]
./DemoLinux64() [0x87cb14]
./DemoLinux64() [0x46a719]
./DemoLinux64() [0x46a916]
./DemoLinux64() [0x46a988]
./DemoLinux64() [0x46826f]
./DemoLinux64() [0x469979]
./DemoLinux64() [0x846489]
/lib64/libpthread.so.0(+0x7dc5) [0x7f57ae312dc5]
/lib64/libc.so.6(clone+0x6d) [0x7f57ad61821d]

16

This issue disappeared after switching to Unity 5.3.1.
Right now we are running 5.3.1p2.

17

I have done more research and found that it depends. On my dell r410 and centos7, it’s ok; but dell r420 and centos7, it crashed. I can’t imagine why this happens. So my guess is that this issue is related with hardware.

18

Maybe it does, but as it was working fine before 5.2 on all those machines it’s some kind of regression that’s been ignored again :frowning:

19

I’m having the same issue with Unity 5.3.2 f1. Are you guys as well?

20

I don’t think it was fixed in 5.3.2, the only solution for now is the no-UI-in-first-scene workaround.