Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X, 2019.2.X
Votes
4
Found in
2017.3.0f1
Issue ID
985931
Regression
Yes
[Linux] Crash in _dl_find_dso_for_object when entering play mode with VR Support enabled
Steps to reproduce:
1. Create a new project
2. Enable VR Support under Player Settings
3. Enter play mode
Result: crash
#0 0x007ffd0b19c240 in funlockfile
#1 0x007ffd0b19c7d0 in _dl_find_dso_for_object
#2 0x007ffd0b19c7e0 in _dl_rtld_di_serinfo
#3 0x007ffd0b19c930 in dlerror
#4 0x007ffd0b19c950 in dlclose
#5 0x007ffd0b19c960 in VR_InitInternal
#6 0x007ffd0b19c9a0 in OpenVR::Initialize(UnityVRDeviceSpecificConfiguration&)
<...>
Reproduced on: 2017.2.0f3, 2017.3.0p2
Did not reproduce on: 2017.1.1f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- No proper error message when mismatching player build and editor version
- MouseMoveEvent returns a positive Position when the Cursor leaves the Window
- Detail Maps packed differently in Built-in vs URP
- Editor crashes when compiling scripts if UNITY_DIAG_ENABLE_DOMAIN_RELOAD_TIMINGS environemnt variable is set
- ScriptableObject serialized fields get unassigned after importing when the 'Auto Refresh' is disabled
Resolution Note (fix version 2019.1):
Updated to OpenVR libs 1.0.14 which resolves this issue.
Resolution Note (fix version 2019.1):
Updated to OpenVR libs 1.0.14 which resolves this issue.