Unity Game Server Crash in PhysX funlockfile on Ubuntu

Anyone have experience with this issue?

1. What happened
Crash when running Unity server in headless mode

Receiving unhandled NULL exception
#0 0x007f0af10a9400 in funlockfile
#1 0x007f0af10a99a0 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#2 0x007f0af10a9ab0 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#3 0x007f0af10a9ac0 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#4 0x007f0af10a9b90 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#5 0x007f0af10ac710 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#6 0x007f0af10acb50 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#7 0x007f0af10acd00 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#8 0x007f0af10acd80 in physx::Cm::CmEventNameProvider::~CmEventNameProvider()
#9 0x007f0af10acda0 in operator delete(void*, std::nothrow_t const&)
#10 0x007f0af10acdb0 in operator delete(void*, std::nothrow_t const&)
#11 0x007f0af10ace60 in operator delete(void*, std::nothrow_t const&)
#12 0x007f0af10acef0 in operator delete(void*, std::nothrow_t const&)
#13 0x007f0af10acf00 in operator delete(void*, std::nothrow_t const&)
#14 0x007f0af10acf20 in start_thread
#15 0x007f0af10acfc0 in clone

2. How we can reproduce it using the example you attached
Unity 2017.3.0p3 built in Linux Ubuntu 16.04.3 LTS
Docker Version 1.13.1

Unknown steps to repro, will try again

License type: Pro

 

I haven't seen this one before - steps to reproduce would be great.

 

@Tak Unfortunately it's a VR project and the repro steps are unknown right now. Does the Linux player have any ability to do a memory dump on failure?

 

Yes, you just need to enable core dumps on your system: https://stackoverflow.com/questions...inux-when-a-process-gets-a-segmentation-fault

 

Great, I'll enable that on our server in case it happens again.