Vizard Segmentation Fault while livestream running

[JeanLoupCaillet]

Hello,

I'm having some issues with Vizard while my simulation is running with Livestream option set to True.
Vizard crashes within a few minutes. I experienced this problem on Vizard 2.1.1, 2.1.2 and 2.1.3.
I tested with and without GDK_BACKEND=x11 prefix but still got the segfault.

My computer specifications are :

Operating System: Ubuntu 20.04
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.14.0-1057-oem
OS Type: 64-bit
Processors: 16 × Intel® Core™ i7-10700K CPU @ 3.80GHz
Memory: 31,1 Gio

Logs in Vizard 2.1.1 are :

Thread 1 (Thread 0x7f79613a0740 (LWP 30739)):
#0  0x00007f79613f848a in __GI___sigsuspend (set=0x7f78a6f6bf00) at ../sysdeps/unix/sysv/linux/sigsuspend.c:26
#1  0x00007f78a6c41268 in GC_suspend_handler_inner () from /home/simulateur-2/Vizard/Vizard_Linux/Vizard_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#2  0x00007f78a6c41302 in GC_suspend_handler () from /home/simulateur-2/Vizard/Vizard_Linux/Vizard_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#3  <signal handler called>
#4  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#5  0x00007f7962f2e08e in UnityClassic::Baselib_SystemFutex_Wait(int*, int, unsigned int) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#6  0x00007f7962d8b121 in GfxDeviceWorker::WaitForEvent(GfxDeviceWorker::EventType) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#7  0x00007f79622092be in GfxDeviceClient::WaitForPendingPresent() () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#8  0x00007f79622091af in GfxDeviceClient::BeginFrame() () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#9  0x00007f79625aa0c4 in PlayerRender(bool) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#10 0x00007f79625a4367 in ExecutePlayerLoop(NativePlayerLoopSystem*) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#11 0x00007f79625a4322 in ExecutePlayerLoop(NativePlayerLoopSystem*) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#12 0x00007f79625a48ce in PlayerLoop() () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#13 0x00007f7962787c03 in PlayerMain(int, char**) () from /home/simulateur-2/Vizard/Vizard_Linux/UnityPlayer.so
#14 0x00007f79613d9083 in __libc_start_main (main=0x2010e0 <main>, argc=1, argv=0x7ffff5cc81d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff5cc81c8) at ../csu/libc-start.c:308
#15 0x0000000000201029 in _start ()
[Inferior 1 (process 30739) detached]

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

Caught fatal signal - signo:11 code:1 errno:0 addr:0x24
Obtained 9 stack frames.
#0  0x007f79615bb420 in (Unknown)
#1  0x007f79624f8e46 in (Unknown)
#2  0x007f79624f8a66 in (Unknown)
#3  0x007f7962d85964 in (Unknown)
#4  0x007f7962d8b1ff in (Unknown)
#5  0x007f7962d814f5 in `(Unknown)`
#6  0x007f7962663daa in (Unknown)
#7  0x007f79615af609 in (Unknown)
#8  0x007f79614d4133 in (Unknown)
Segmentation Fault

Let me know if you want more information.
Thanks !

[schaubh]

Mm, I don't have access to such a Linux system so I can't duplicate this on our side.

[woodj80]

I'm sorry that livestreaming your sim with Vizard isn't working correctly. Would you mind providing the Player.log that got generated after an attempt to livestream your sim? On a Linux machine, it should be located at:

~/.config/unity3d/Vizard/Vizard/Player.log

Thanks!

[JeanLoupCaillet]

Hello,

Thanks for your feedback !
I'm a bit new with Vizard. I can provide 2 files.
The heavy one (Player-prev.log), represents different attempts .
Indeed, we changed our desktop environment due to a python module installation causing a malfunction in the logging process on Ubuntu.
So we thought Wayland desktop was the problem, but KDE plasma did the same result.

And the light one (Player.log) should represent gdm3 environment.

If you need further information don't hesitate to ask :)
Thanks for your help,

Player-prev.log
Player.log

[woodj80]

Thank you for providing the log files! I can see that Vizard itself seems to start up without errors and loads your obj model in, but then has a problem within the NetMQ library that provides the network connection and terminates. It is possible that there is a configuration issue. I will investigate this and report back to you when I know more. Thank you for reporting the problem and for providing all the supporting information.

[woodj80]

I wanted to provide you with an update: I was able to successfully run the live streaming example scenarioBasicOrbitStream.py (in Basilisk examples) with the latest Vizard (2.1.4) on Linux. The system used was running Ubuntu 20.04 using the Windows Subsystem for Linux WSL1. I will continue working on this, but if you could try running scenarioBasicOrbitStream.py it may help us figure out if it is a local configuration issue.

[JeanLoupCaillet]

Hello,
Thanks for your time. I changed the graphical desktop environment back to gdm3. It seems working for now. But I can switch back easily and try running the OrbitStream scenario.
I'll provide the logs this week.
Best,